@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 51 of 244)
| Version | Deps | Published |
|---|---|---|
| 1.0.1065 | 18 / 6 | |
| 1.0.1060 | 18 / 6 | |
| 1.0.1053 | 18 / 6 | |
| 1.0.1050 | 18 / 6 | |
| 1.0.1049 | 18 / 6 | |
| 1.0.1029 | 18 / 6 | |
| 1.0.1021 | 18 / 6 | |
| 1.0.1018 | 18 / 6 | |
| 1.0.1008 | 18 / 6 | |
| 1.0.999 | 18 / 6 | |
| 1.0.990 | 18 / 6 | |
| 1.0.972 | 18 / 6 | |
| 1.0.971 | 18 / 6 | |
| 1.0.970 | 18 / 6 | |
| 1.0.968 | 18 / 6 | |
| 1.0.932 | 18 / 6 | |
| 1.0.818 | 18 / 6 | |
| 1.0.581 | 18 / 6 | |
| 1.0.489 | 18 / 6 | |
| 1.0.488 | 18 / 6 | |
| 1.0.487 | 17 / 6 | |
| 1.0.486 | 17 / 6 | |
| 1.0.485 | 17 / 6 | |
| 1.0.484 | 17 / 6 | |
| 1.0.483 | 17 / 6 | |
| 1.0.482 | 17 / 6 | |
| 1.0.481 | 17 / 6 | |
| 1.0.480 | 17 / 6 | |
| 1.0.479 | 17 / 6 | |
| 1.0.478 | 17 / 6 | |
| 1.0.477 | 17 / 6 | |
| 1.0.476 | 17 / 6 | |
| 1.0.475 | 17 / 6 | |
| 1.0.474 | 17 / 6 | |
| 1.0.473 | 17 / 6 | |
| 1.0.472 | 17 / 6 | |
| 1.0.471 | 17 / 6 | |
| 1.0.470 | 17 / 6 | |
| 1.0.469 | 17 / 6 | |
| 1.0.468 | 17 / 6 | |
| 1.0.467 | 17 / 6 | |
| 1.0.466 | 17 / 6 | |
| 1.0.465 | 17 / 6 | |
| 1.0.464 | 17 / 6 | |
| 1.0.463 | 17 / 6 | |
| 1.0.462 | 17 / 6 | |
| 1.0.461 | 17 / 6 | |
| 1.0.460 | 17 / 6 | |
| 1.0.459 | 17 / 6 | |
| 1.0.458 | 17 / 6 | |
| 1.0.457 | 17 / 6 |
v1.0.1065
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1053
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1050
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1049
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.581
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.489
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.488
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 (shohamgilad) than the most recent previously approved version (davidfirst) on 2024-12-10, but shohamgilad 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.487
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.486
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.485
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.484
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.483
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.482
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.481
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.480
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.479
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.478
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.477
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.476
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.475
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.474
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.473
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.472
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.471
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.470
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.469
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.468
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.467
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.466
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.465
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.464
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.463
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.462
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.461
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.460
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.459
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.458
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.457
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.