@tramvai/test-integration-jest
Jest preset for integration-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@swc-node/jest | AI (dependencies): @swc-node/jest is a legitimate SWC-based Jest transformer; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large monorepo package with no provenance history; consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): Known implicit SWC runtime dep; declared in package.json, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit SWC helpers dep; standard pattern for SWC-based tooling. | ai |
Versions (showing 7 of 111)
| Version | Deps | Published |
|---|---|---|
| 5.53.117 | 8 / 1 | |
| 5.53.116 | 8 / 1 | |
| 5.53.115 | 8 / 1 | |
| 5.53.114 | 8 / 1 | |
| 5.53.112 | 8 / 1 | |
| 5.53.111 | 8 / 1 | |
| 5.53.94 | 8 / 1 |
v5.53.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.