Skip to content

Releases: modem-dev/slop-scan

v0.4.0

30 Apr 02:19
0e8d699

Choose a tag to compare

What's Changed

Full Changelog: v0.3.0...v0.4.0

v0.3.0

16 Apr 15:18

Choose a tag to compare

Highlights

  • add slop-scan delta for comparing two scans or saved reports, with text/JSON output and --fail-on policies for CI
  • add plugin loading, preset configs via extends, rule options, and support for slop-scan.config.ts/js/mjs/cjs/json
  • add path-scoped rule overrides
  • refine documented empty-catch fallback handling and ignore cleanup-only duplicated mock setup in tests
  • add GitHub Actions CI for format, lint, test, and build

Validation

  • bun run format:check
  • bun run lint
  • bun run test
  • bun run build

Full changelog

v0.2.0

08 Apr 22:09

Choose a tag to compare

Minor release focused on repo dogfooding, developer workflow, and better defensive-code heuristics.

Highlights:

  • Respect .gitignore during discovery and switch discovery to globby
  • Add AGENTS/CLAUDE guidance, Oxc linting, and pre-commit hooks
  • Add stable self-scan regression checks against the last published release
  • Split defensive try/catch heuristics into error-swallowing, error-obscuring, and empty-catch rules

v0.1.3

08 Apr 22:09

Choose a tag to compare

Performance-focused release.

Highlights:

  • Scanner throughput optimization pass
  • Benchmark refresh for the faster scan pipeline

v0.1.2

08 Apr 22:09

Choose a tag to compare

Feature and packaging release leading to the current slop-scan identity.

Highlights:

  • Add duplicate helper-signature detection
  • Add lint-style reporter and grouped multi-file locations
  • Improve README/CLI docs and add MIT license
  • Rename the project/package to slop-scan

v0.1.1

08 Apr 22:09

Choose a tag to compare

Packaging follow-up release.

Highlights:

  • First tagged 0.1.1 release cut
  • Fix npm bin entry for the published CLI

v0.1.0

08 Apr 22:09

Choose a tag to compare

Initial public release of the analyzer.

Highlights:

  • Pluggable scan engine with language, fact, rule, and reporter components
  • Initial heuristic pack and fixture regression suite
  • Pinned benchmark set with normalized repo metrics
  • npm packaging setup and streamed analysis to avoid OOMs