@nsshunt/ststestrunner
STS Test Runner Module
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:k6 | AI (phantom-deps): k6 is a load-testing runtime stub; declared for types, not imported directly in Node.js code — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:seedrandom | AI (phantom-deps): Utility used in test configs/scripts rather than directly imported in source; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:http-status-codes | AI (phantom-deps): Imported indirectly through config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nsshunt/stssocketioutils | AI (phantom-deps): Same-org internal dependency; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nsshunt/stsauthclient | AI (phantom-deps): Same-org internal dependency; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:fast-json-patch | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai |
Versions (showing 7 of 152)
| Version | Deps | Published |
|---|---|---|
| 1.1.7 | 12 / 14 | |
| 1.1.6 | 11 / 14 | |
| 1.1.5 | 11 / 14 | |
| 1.1.4 | 11 / 14 | |
| 1.1.3 | 11 / 14 | |
| 1.1.2 | 11 / 14 | |
| 1.1.1 | 11 / 14 |
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.