@yamf/test
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @yamf/test; 'test' is a generic word, not a typo of 'jest'. Stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Same reasoning; 'test' vs 'next' is incidental Levenshtein proximity, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Same reasoning; scoped package with legitimate identity, not a vitest typosquat. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 0 / 0 | |
| 0.1.4 | 0 / 0 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 1 | |
| 0.1.0 | 0 / 1 |
v0.9.0
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@yamf/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.