Repository navigation
Build against scanner-core 0.7.0 - #11
Merged
Merged
Conversation
0.7 is the floor for the file types the 2026.11.18.001 rules target — container builds, devcontainers, compose files, nested READMEs and agent command/skill markdown — and for the `.dockerfile.sh` / `.compose.yml` rule scopes. The core is bundled at build time, so a CLI built against 0.6.x would ship without them. Verified against the published tarball: npm ci, typecheck, 59 tests, build and the built-CLI smoke test all pass. The bundle grows by about 1 KB.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the bundled core from
^0.6.0to^0.7.0and refreshes the lock.0.7 is the floor for the file types the
2026.11.18.001rules target — container builds, devcontainers, compose files, nested READMEs and agent command/skill markdown — and for the.dockerfile.sh/.compose.ymlrule scopes. The core is bundled at build time, so a CLI built against 0.6.x would ship without any of it: the rules would load and then never match.It also carries the per-scan file-cap change. Sources are now read in priority order — build and install scripts, then ordinary source, then tests and samples, then generated or vendored artifacts — so a capped scan spends its 200 requests on the code that runs on a clone rather than on test files every rule skips.
Verification
Against the published
@flagrix/scanner-core@0.7.0tarball, the full CI sequence locally:npm ci— resolves cleanly with the refreshed locknpm run typecheck— cleannpm test— 59 tests passnpm run build+node dist/cli.js --version && --help— the smoke test CI runsBundle grows by about 1 KB (279.79 → 280.62 KB).
Note on shipping
Merging this does not reach npm users. The core is bundled, so
flagrix@0.5.1keeps shipping 0.6.0 scanning until a release goes out: version bump, then av*tag to triggerrelease.yml(npm publish with provenance, plus the MCP registry publish).