← Home

@teambit/api-reference.renderers.class

npm Repository Homepage
3
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 pattern across the ecosystem. ai
provenance no-provenance AI (provenance): Teambit packages do not use Sigstore provenance; consistent across all versions. ai
maintainer-change maintainer-removed AI (maintainer-change): Teambit org regularly rotates maintainers across its large component portfolio; not indicative of takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy consistent with org-level release cadence changes; publisher has strong track record and official repo. 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 3 of 3)

Version Deps Published
0.0.84 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.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.