@teambit/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @teambit/* internal dep, consistent with monorepo lockstep releases. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit publishes hundreds of components in automated batches; rapid successive publishes are normal for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with clear keywords and repo; missing description is stable metadata issue. | ai | |
| provenance | no-provenance | AI (provenance): Low-severity metadata gap; package has legitimate GitHub repo and long history. | ai | |
| phantom-deps | phantom-dep:jest-watcher | AI (phantom-deps): jest-watcher loaded by jest framework convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@jest/test-result | AI (phantom-deps): Framework-scoped package loaded by convention; stable for this package. | ai | |
| dependencies | unvetted-dep:@teambit/component | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): @teambit/jest is the official Jest integration for Bit; no relation to 'next', stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/tests-results | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/tester | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/worker | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* monorepo dep; expected unvetted status for this ecosystem. | ai |
Versions (showing 44 of 244)
| Version | Deps | Published |
|---|---|---|
| 1.0.300 | 17 / 8 | |
| 1.0.299 | 17 / 8 | |
| 1.0.298 | 17 / 8 | |
| 1.0.297 | 17 / 8 | |
| 1.0.296 | 17 / 8 | |
| 1.0.295 | 17 / 8 | |
| 1.0.294 | 17 / 8 | |
| 1.0.293 | 17 / 8 | |
| 1.0.292 | 17 / 8 | |
| 1.0.291 | 17 / 8 | |
| 1.0.290 | 17 / 8 | |
| 1.0.289 | 17 / 8 | |
| 1.0.288 | 17 / 8 | |
| 1.0.287 | 17 / 8 | |
| 1.0.286 | 17 / 8 | |
| 1.0.285 | 17 / 8 | |
| 1.0.284 | 17 / 8 | |
| 1.0.283 | 17 / 8 | |
| 1.0.282 | 17 / 8 | |
| 1.0.281 | 17 / 8 | |
| 1.0.280 | 17 / 8 | |
| 1.0.279 | 17 / 8 | |
| 1.0.278 | 17 / 8 | |
| 1.0.277 | 17 / 8 | |
| 1.0.276 | 17 / 8 | |
| 1.0.275 | 17 / 8 | |
| 1.0.274 | 17 / 8 | |
| 1.0.273 | 17 / 8 | |
| 1.0.272 | 17 / 8 | |
| 1.0.271 | 17 / 8 | |
| 1.0.270 | 17 / 8 | |
| 1.0.269 | 17 / 8 | |
| 1.0.268 | 17 / 8 | |
| 1.0.267 | 17 / 8 | |
| 1.0.266 | 17 / 8 | |
| 1.0.265 | 17 / 8 | |
| 1.0.264 | 17 / 8 | |
| 1.0.263 | 17 / 8 | |
| 1.0.262 | 17 / 8 | |
| 1.0.261 | 17 / 8 | |
| 1.0.260 | 17 / 8 | |
| 1.0.259 | 17 / 8 | |
| 1.0.258 | 17 / 8 | |
| 1.0.257 | 17 / 8 |
v1.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.297
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.296
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-02, but davidfirst is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.259
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-01, but davidfirst is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.