← Home

@teambit/api-reference.renderers.enum

npm Repository Homepage
7
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
provenance no-provenance AI (provenance): Teambit publishes many packages without provenance; consistent across their ecosystem, not a risk indicator here. ai
provenance publisher-changed AI (provenance): davidfirst is a long-standing teambit contributor (263 approved packages); publisher rotation within the org is expected. ai
npm-metadata no-description AI (npm-metadata): Teambit component packages consistently omit descriptions; stable false positive for this publisher. ai
maintainer-change maintainer-removed AI (maintainer-change): Teambit org regularly rotates maintainers across its large component library; not indicative of takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Batch publishing cadence for teambit components; dormancy followed by org-level release is normal for this package. 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 7 of 7)

Version Deps Published
0.0.84 6 / 7
0.0.82 6 / 7
0.0.80 6 / 7
0.0.77 6 / 7
0.0.73 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.82

2 findings
HIGH Publisher changed: teambit-owner → davidfirst (on 2025-08-19) provenance

This version was published by a different npm account than previous versions on 2025-08-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.80

1 finding
LOW No provenance attestation provenance

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

v0.0.77

1 finding
LOW No provenance attestation provenance

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

v0.0.73

2 findings
HIGH Publisher changed: teambit-owner → davidfirst (on 2025-07-14) provenance

This version was published by a different npm account than previous versions on 2025-07-14. This could indicate a legitimate maintainer transition or an account compromise.

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.