@teambit/documenter.ui.sub-title
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
teambit-ownershohamgiladdavidfirstlalybarranm8odedreguysaaritaymendelerezbitgitedenjoshk2redigmayona007jonisarbenjgilocombe
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): Teambit component packages consistently omit descriptions; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance across all their packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit dependency in Bit.dev components; stable false positive for this package family. | ai |
v4.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.