@tramvai/test-unit-jest
Jest preset for unit-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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo package; version gaps are expected across many sub-packages in a monorepo release cadence. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived tramvai monorepo package; no provenance is consistent across all versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Both new deps are established ecosystem packages; addition is consistent with a Jest testing preset upgrade. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): SWC core is a known implicit runtime dep for @swc-node/jest transformer; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@jest/types | AI (phantom-deps): Framework-scoped Jest types package; loaded by convention in Jest preset packages. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit SWC runtime helper dependency; stable false positive for this package. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 5.53.140 | 5 / 0 | |
| 5.53.123 | 5 / 0 | |
| 5.53.122 | 5 / 0 | |
| 5.53.120 | 5 / 0 | |
| 5.53.118 | 5 / 0 | |
| 5.53.117 | 5 / 0 | |
| 5.53.116 | 5 / 0 | |
| 5.53.115 | 5 / 0 | |
| 5.53.114 | 5 / 0 | |
| 5.53.112 | 5 / 0 | |
| 5.53.111 | 5 / 0 | |
| 5.53.94 | 5 / 0 |
v5.53.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.116
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.112
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.