Repository navigation
fix(engine): calibrate test context and harden reproducibility - #5
Merged
Merged
Conversation
Keep test paths analyzed while ranking already-abstained test-only evidence after production paths, add neutral regressions, document npm CLI pre/post accounting, and retire fixture dependency alert noise with patched versions and explicit execution warnings. Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
Use every retained evidence-path step for test-context ordering, cover mixed paths, advance the inert Django fixture to verified patched 5.2.17, and pin the CI toolchain and dependency gates. Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
Record the clean-commit rebuild identity and final frozen npm scan hash, resource sample, and byte accounting without changing scanner source. Signed-off-by: Daniel Castrillon <danielcadev@users.noreply.github.com>
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.
Summary
Authorized npm CLI evidence
The final run analyzed npm CLI commit
b888cc9a9ff34a8b023ff47b784692396635397bwith Engine source commitc3aa5f7ee54139eac2e0398d6e4bc09969488cefand evidence binding commitadf92157366251538946d4707de643ba05700c05.It recorded:
The report SHA-256 is
5f13488477fb859bab640875e3482fc87f85bf5c6a691c613e95c596b086084f.Verification
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --locked -- -D warningscargo test --workspace --locked— 238 passedcargo audit— 426 dependencies and 1,226 advisories, with only the two documented build-time exceptions RUSTSEC-2026-0194 and RUSTSEC-2026-0195cargo deny check— passedDependency-alert boundary
The existing GitHub alerts originate from inert fixture manifests that are not installed or executed. This PR updates and documents those fixtures but does not dismiss hosted alerts. GitHub must recompute their state after merge.
Claim boundary
Zero findings is not a clean verdict or a complete security audit. All three npm leads remain abstentions requiring human judgment. This PR does not establish human superiority, production safety, or general scanner effectiveness.