@teambit/diagnostic
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 | rapid-publish | AI (publish-pattern): teambit publishes hundreds of coordinated monorepo releases rapidly via automation; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit.get-bit-version | AI (dependencies): First-party teambit package; stable dependency across versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Auto-generated component package from teambit/bit monorepo; missing description is a stable pattern across all @teambit/* packages. | ai | |
| provenance | no-provenance | AI (provenance): teambit/bit publishes thousands of component packages without Sigstore provenance; stable pattern for this publisher. | ai |
Versions (showing 100 of 238)
| Version | Deps | Published |
|---|---|---|
| 1.0.782 | 6 / 2 | |
| 1.0.780 | 6 / 2 | |
| 1.0.777 | 6 / 2 | |
| 1.0.775 | 6 / 2 | |
| 1.0.772 | 6 / 2 | |
| 1.0.766 | 6 / 2 | |
| 1.0.763 | 6 / 2 | |
| 1.0.761 | 6 / 2 | |
| 1.0.760 | 6 / 2 | |
| 1.0.756 | 6 / 2 | |
| 1.0.754 | 6 / 2 | |
| 1.0.752 | 6 / 2 | |
| 1.0.750 | 6 / 2 | |
| 1.0.749 | 6 / 2 | |
| 1.0.746 | 6 / 2 | |
| 1.0.744 | 6 / 2 | |
| 1.0.743 | 6 / 2 | |
| 1.0.739 | 6 / 2 | |
| 1.0.736 | 6 / 2 | |
| 1.0.733 | 6 / 2 | |
| 1.0.732 | 6 / 2 | |
| 1.0.730 | 6 / 2 | |
| 1.0.726 | 6 / 2 | |
| 1.0.725 | 6 / 2 | |
| 1.0.724 | 6 / 2 | |
| 1.0.723 | 6 / 2 | |
| 1.0.720 | 6 / 2 | |
| 1.0.718 | 6 / 2 | |
| 1.0.715 | 6 / 2 | |
| 1.0.714 | 6 / 2 | |
| 1.0.711 | 6 / 2 | |
| 1.0.708 | 6 / 2 | |
| 1.0.707 | 6 / 2 | |
| 1.0.705 | 6 / 2 | |
| 1.0.699 | 6 / 2 | |
| 1.0.698 | 6 / 2 | |
| 1.0.693 | 6 / 2 | |
| 1.0.692 | 6 / 2 | |
| 1.0.690 | 6 / 2 | |
| 1.0.688 | 6 / 2 | |
| 1.0.687 | 6 / 2 | |
| 1.0.686 | 6 / 2 | |
| 1.0.680 | 6 / 2 | |
| 1.0.679 | 6 / 2 | |
| 1.0.674 | 6 / 2 | |
| 1.0.670 | 6 / 2 | |
| 1.0.669 | 6 / 2 | |
| 1.0.667 | 6 / 2 | |
| 1.0.665 | 6 / 2 | |
| 1.0.656 | 6 / 2 | |
| 1.0.655 | 6 / 2 | |
| 1.0.654 | 6 / 2 | |
| 1.0.652 | 6 / 2 | |
| 1.0.650 | 6 / 2 | |
| 1.0.647 | 6 / 2 | |
| 1.0.644 | 6 / 2 | |
| 1.0.643 | 6 / 2 | |
| 1.0.641 | 6 / 2 | |
| 1.0.640 | 6 / 2 | |
| 1.0.637 | 6 / 2 | |
| 1.0.634 | 6 / 2 | |
| 1.0.633 | 6 / 2 | |
| 1.0.631 | 6 / 2 | |
| 1.0.627 | 6 / 2 | |
| 1.0.625 | 6 / 2 | |
| 1.0.623 | 6 / 2 | |
| 1.0.621 | 6 / 2 | |
| 1.0.617 | 6 / 2 | |
| 1.0.616 | 6 / 2 | |
| 1.0.614 | 6 / 2 | |
| 1.0.612 | 6 / 2 | |
| 1.0.610 | 6 / 2 | |
| 1.0.322 | 5 / 3 | |
| 1.0.321 | 5 / 3 | |
| 1.0.320 | 5 / 3 | |
| 1.0.319 | 5 / 3 | |
| 1.0.318 | 5 / 3 | |
| 1.0.317 | 5 / 3 | |
| 1.0.316 | 5 / 3 | |
| 1.0.315 | 5 / 3 | |
| 1.0.314 | 5 / 3 | |
| 1.0.313 | 5 / 3 | |
| 1.0.312 | 5 / 3 | |
| 1.0.311 | 5 / 3 | |
| 1.0.310 | 5 / 3 | |
| 1.0.309 | 5 / 3 | |
| 1.0.308 | 5 / 3 | |
| 1.0.307 | 5 / 3 | |
| 1.0.306 | 5 / 3 | |
| 1.0.305 | 5 / 3 | |
| 1.0.304 | 5 / 3 | |
| 1.0.303 | 5 / 3 | |
| 1.0.302 | 5 / 3 | |
| 1.0.301 | 5 / 3 | |
| 1.0.300 | 5 / 3 | |
| 1.0.299 | 5 / 3 | |
| 1.0.298 | 5 / 3 | |
| 1.0.297 | 5 / 3 | |
| 1.0.296 | 5 / 3 | |
| 1.0.295 | 5 / 3 |
v1.0.322
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.321
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.320
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.319
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.318
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.317
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.316
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.315
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.314
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.313
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.312
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.311
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.310
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.309
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.308
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.307
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.306
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.305
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.304
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.303
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.302
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.301
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.300
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.299
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.298
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.297
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.296
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.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.