@cedarjs/testing
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:dynamic-require | AI (semgrep): Dynamic require in Jest setup loads user project db by convention path; standard test framework pattern, not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Type package loaded by convention; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type package loaded by convention; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): Type package loaded by convention; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:@types/babel-core | AI (phantom-deps): Type package loaded by convention; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:ansis | AI (phantom-deps): Referenced in config files; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:babel-jest | AI (phantom-deps): Referenced in Jest config files; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:jest-watch-typeahead | AI (phantom-deps): Referenced in Jest config; stable false positive for this testing package. | ai | |
| phantom-deps | phantom-dep:@testing-library/user-event | AI (phantom-deps): Testing library loaded by convention; stable false positive for this testing package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 24 / 7 | |
| 4.1.0 | 24 / 7 | |
| 4.0.0 | 24 / 7 | |
| 3.1.1 | 24 / 7 | |
| 3.1.0 | 24 / 7 | |
| 3.0.0 | 24 / 7 | |
| 2.8.1 | 24 / 7 | |
| 2.8.0 | 24 / 7 | |
| 2.7.0 | 24 / 7 | |
| 2.6.0 | 24 / 7 | |
| 2.5.1 | 24 / 7 | |
| 2.5.0 | 24 / 7 | |
| 2.4.1 | 24 / 7 | |
| 2.4.0 | 24 / 7 | |
| 2.3.0 | 24 / 7 | |
| 2.2.1 | 24 / 7 | |
| 2.2.0 | 24 / 7 | |
| 2.1.1 | 24 / 7 | |
| 2.1.0 | 24 / 7 | |
| 2.0.3 | 24 / 7 | |
| 2.0.2 | 24 / 7 | |
| 2.0.1 | 24 / 7 | |
| 2.0.0 | 24 / 7 | |
| 1.1.2 | 24 / 7 | |
| 1.1.1 | 24 / 7 | |
| 1.1.0 | 24 / 7 | |
| 1.0.0 | 24 / 7 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.