@handy-common-utils/dev-dependencies-jest
This package contains dependencies that are common, including jest
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely a CI/CD environment change; no security impact for a dev-dependencies meta-package. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): This package is a dev-dependency bundle; jest is a declared peer/runtime dep, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@jest/globals | AI (phantom-deps): Framework-scoped package bundled for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@handy-common-utils/dev-dependencies-common | AI (phantom-deps): Same-org sibling dep bundled for re-export; phantom-dep false positive for this package type. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.9.12 | 4 / 2 | |
| 1.9.11 | 4 / 2 | |
| 1.9.10 | 4 / 2 | |
| 1.9.9 | 4 / 2 | |
| 1.9.8 | 4 / 2 | |
| 1.9.7 | 4 / 2 | |
| 1.9.6 | 4 / 2 | |
| 1.8.0 | 4 / 2 | |
| 1.7.1 | 4 / 2 | |
| 1.7.0 | 4 / 2 | |
| 1.6.5 | 4 / 2 | |
| 1.6.4 | 4 / 2 | |
| 1.6.3 | 4 / 2 | |
| 1.6.2 | 4 / 2 | |
| 1.6.1 | 4 / 2 | |
| 1.5.0 | 4 / 2 | |
| 1.4.0 | 4 / 2 |
v1.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: james-hu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: james-hu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.