← Home

@teambit/api-reference.renderers.interface

npm Repository Homepage
5
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-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Keywords

bitcomponentscollaborationwebreactreact-componentsangularangular-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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; not a risk indicator here. ai
maintainer-change maintainer-removed AI (maintainer-change): Teambit org restructuring; consistent across many packages in the same org with no malicious indicators. ai
publish-pattern dormant-publish AI (publish-pattern): Long dormancy followed by resumed publishing is consistent with org-level release cadence changes, not takeover. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): core-js is a known implicit runtime/polyfill dependency; stable false positive for this package. ai

Versions (showing 5 of 5)

Version Deps Published
0.0.84 6 / 7
0.0.76 6 / 7
0.0.75 6 / 7
0.0.72 6 / 7
0.0.70 6 / 7

v0.0.84

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.76

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.75

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.72

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.70

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.