@teambit/react.ui.docs-app
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Stable teambit component package; missing description is a consistent pattern across their components, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established teambit publisher; no provenance is consistent across their entire component library. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted teambit publisher with 258 approved packages; dormancy consistent with monorepo release cadence, not account takeover. | 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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.38 | 7 / 8 | |
| 1.0.37 | 7 / 8 | |
| 1.0.36 | 7 / 8 | |
| 1.0.34 | 7 / 8 | |
| 1.0.33 | 7 / 8 | |
| 1.0.32 | 7 / 6 | |
| 1.0.31 | 7 / 6 | |
| 1.0.28 | 7 / 6 |
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.