@teambit/code.ui.code-compare
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/design.themes.theme-toggler | AI (dependencies): Same-org @teambit scoped dependency; consistent with teambit's component-based architecture. | ai | |
| dependencies | unvetted-dep:@teambit/base-react.content.image | AI (dependencies): Same-org @teambit scoped dependency; consistent with teambit's component-based architecture. | ai | |
| dependencies | unvetted-dep:@teambit/design.themes.dark-theme | AI (dependencies): Same-org @teambit scoped dependency; consistent with teambit's component-based architecture. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consolidation to org-level teambit-owner account; consistent with org-wide publisher migration. | ai | |
| provenance | publisher-changed | AI (provenance): teambit-owner is the org account for teambit; transition from individual to org publisher is expected and stable. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages routinely omit descriptions; stable pattern across this publisher's packages. | ai | |
| phantom-deps | phantom-dep:@teambit/ui-foundation.ui.constants.z-indexes | AI (phantom-deps): Same-org @teambit scope; likely used indirectly via CSS/style imports not caught by static analysis. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all @teambit/* packages; not a risk signal for this publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.346 | 29 / 5 | |
| 0.0.344 | 29 / 5 | |
| 0.0.342 | 29 / 5 | |
| 0.0.341 | 29 / 5 | |
| 0.0.339 | 29 / 5 | |
| 0.0.338 | 29 / 5 | |
| 0.0.334 | 29 / 5 | |
| 0.0.325 | 30 / 5 |
v0.0.346
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.344
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.342
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.341
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.339
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.338
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.334
2 findingsThis version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.