@teambit/preview.ui.component-preview
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages consistently omit descriptions; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance across all their packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a declared runtime polyfill dependency; phantom-dep false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.0.33 | 7 / 11 | |
| 1.0.32 | 7 / 11 | |
| 1.0.31 | 6 / 11 | |
| 1.0.30 | 6 / 11 | |
| 1.0.29 | 6 / 11 | |
| 1.0.28 | 6 / 11 | |
| 1.0.27 | 6 / 11 | |
| 1.0.26 | 6 / 11 | |
| 1.0.24 | 6 / 11 | |
| 1.0.23 | 6 / 11 | |
| 1.0.21 | 6 / 11 | |
| 1.0.20 | 6 / 11 | |
| 1.0.19 | 6 / 11 | |
| 1.0.17 | 6 / 11 | |
| 1.0.16 | 6 / 11 | |
| 1.0.15 | 6 / 11 | |
| 1.0.14 | 6 / 11 | |
| 1.0.13 | 6 / 11 |
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
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 (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-02-03, but teambit-owner 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.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
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.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.