Repository navigation
test: use a Scorecard-recognised extension for property fuzzing - #80
Merged
Merged
Conversation
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
Rename the existing
fast-checkproperty suite to.js. Scorecard v5.6.0 scans JavaScript.jsand.jsxfiles for directfast-checkimports, so it did not detect the current.mjsfile (detector source). The test contents are unchanged.Motivation
Make the existing bounded, deterministic property tests visible to Scorecard’s detector without adding tests or artificial fuzzing signals.
Changes
tests/property-fuzz.test.mjstotests/property-fuzz.test.js; the file is byte-for-byte identical.Tests performed
npm ci --ignore-scripts, direct property-test discovery (3 passed),npm test(122 passed),npm run coverage,npm run lint,npm audit --audit-level=high(0 vulnerabilities),npm run package:check,npm run package:smoke,npm run action:checkandnpm run format:check.package.json,package-lock.jsonanddistare unchanged. The package dry run does not include the test file.Compatibility
package.jsonalready declares"type": "module"and Node>=22. The renamed ESM test ran on Node 22 and 24.Security and privacy
Only the test filename changes. The deterministic seed, generated input bounds and assertions are unchanged.
Shopify source/evidence
N/A; this is a test filename change.
Release impact
Tests only. No npm package contents, package version, runtime behaviour or release workflow changes; no release is needed.
Checklist