@teambit/api-reference.renderers.type-literal
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/api-reference.overview.renderers.grouped-schema-nodes-overview-summary | AI (dependencies): Sibling @teambit org package; consistent with this component's established dependency pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Teambit publishes many components in bulk; dormancy reflects org release cadence, not account takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level maintainer consolidation under teambit-owner; consistent pattern across teambit packages. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill runtime dep; phantom-dep false positive stable for this package family. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.75 | 6 / 7 | |
| 0.0.66 | 6 / 7 | |
| 0.0.62 | 6 / 7 | |
| 0.0.61 | 6 / 7 |
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.