@teambit/workspace.ui.workspace-component-card
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/scopes.scope-id | AI (dependencies): First-party teambit scoped package; consistent with the rest of the teambit dependency graph. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages consistently omit descriptions; not a malware signal for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance across all their packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known runtime polyfill dependency; phantom-dep firing here is a stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.571 | 6 / 8 | |
| 0.0.570 | 6 / 8 | |
| 0.0.569 | 6 / 8 | |
| 0.0.568 | 6 / 8 | |
| 0.0.566 | 6 / 8 | |
| 0.0.565 | 6 / 8 | |
| 0.0.564 | 6 / 8 | |
| 0.0.550 | 6 / 8 |
v0.0.571
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.570
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.568
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.566
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.565
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.564
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.550
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.