@teambit/component.ui.version-block
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/design.ui.contributors | AI (dependencies): Internal @teambit scoped dependency; consistent with teambit's component publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/base-react.navigation.link | AI (dependencies): Internal @teambit scoped dependency; consistent with teambit's component publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped component package from teambit; missing description is a consistent pattern across their component library, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes hundreds of scoped packages without provenance; consistent pattern, not a risk indicator. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill implicit dependency; stable false positive for this package. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.0.950 | 10 / 8 | |
| 0.0.949 | 10 / 8 | |
| 0.0.948 | 10 / 8 | |
| 0.0.947 | 10 / 8 | |
| 0.0.946 | 10 / 8 | |
| 0.0.945 | 9 / 8 | |
| 0.0.944 | 9 / 8 | |
| 0.0.943 | 9 / 8 | |
| 0.0.942 | 9 / 8 | |
| 0.0.941 | 9 / 8 | |
| 0.0.940 | 9 / 8 | |
| 0.0.934 | 10 / 8 | |
| 0.0.933 | 10 / 8 | |
| 0.0.931 | 10 / 8 | |
| 0.0.927 | 10 / 8 | |
| 0.0.926 | 10 / 8 | |
| 0.0.922 | 10 / 8 | |
| 0.0.918 | 10 / 8 | |
| 0.0.916 | 10 / 8 | |
| 0.0.915 | 11 / 8 | |
| 0.0.914 | 10 / 8 | |
| 0.0.912 | 10 / 8 | |
| 0.0.911 | 10 / 8 | |
| 0.0.910 | 10 / 8 | |
| 0.0.909 | 10 / 8 | |
| 0.0.908 | 10 / 8 | |
| 0.0.907 | 10 / 8 | |
| 0.0.906 | 10 / 8 | |
| 0.0.905 | 10 / 8 | |
| 0.0.904 | 10 / 8 | |
| 0.0.903 | 10 / 8 | |
| 0.0.902 | 10 / 8 | |
| 0.0.901 | 10 / 8 | |
| 0.0.900 | 10 / 8 | |
| 0.0.899 | 10 / 8 | |
| 0.0.898 | 10 / 8 | |
| 0.0.897 | 10 / 8 | |
| 0.0.896 | 10 / 8 | |
| 0.0.895 | 10 / 8 | |
| 0.0.894 | 10 / 8 | |
| 0.0.893 | 10 / 8 | |
| 0.0.891 | 10 / 8 | |
| 0.0.890 | 10 / 8 | |
| 0.0.889 | 10 / 8 | |
| 0.0.888 | 10 / 8 |
v0.0.950
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.949
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.948
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.947
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.914
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-04-16, 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.
v0.0.912
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.911
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.910
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.909
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.908
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.907
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.906
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.905
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.904
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.903
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.902
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.901
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.900
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.899
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.898
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.897
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.896
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.895
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.894
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.893
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.891
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.890
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.889
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.888
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.