@nimee/tests
Tests common
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): All raw-IP references are 127.0.0.1 (localhost) with env-var ports — expected for a local test-service helper package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped internal package @nimee/tests; not impersonating jest, just a test utility that depends on it. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): jest is a declared runtime dep used via jest config; not directly imported in source but legitimately referenced. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv loaded via config/env setup, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-jest | AI (phantom-deps): ts-jest is a jest transformer declared in jest config; not directly imported in source. | ai | |
| phantom-deps | phantom-dep:jest-junit | AI (phantom-deps): jest-junit is a jest reporter declared in config; not directly imported in source. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.39 | 10 / 8 | |
| 0.0.38 | 10 / 8 | |
| 0.0.37 | 10 / 8 | |
| 0.0.35 | 10 / 8 | |
| 0.0.34 | 10 / 8 | |
| 0.0.33 | 10 / 8 |
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.