@teambit/react.ui.error-fallback
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): teambit-owner is the org account for teambit; publisher consolidation is expected across their component packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of lalybar consistent with org-level consolidation to teambit-owner; no malicious indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by org account consolidation; no code changes or suspicious additions. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages consistently omit descriptions; not a malware signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.136 | 5 / 8 | |
| 0.0.135 | 5 / 8 | |
| 0.0.134 | 5 / 8 | |
| 0.0.133 | 5 / 8 | |
| 0.0.132 | 5 / 8 |
v0.0.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.134
2 findingsThis version was published by a different npm account than previous versions on 2025-11-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.