← Home

@teambit/code.ui.queries.get-component-code

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

learn-bitteambit-ownershohamgiladdavidfirstlalybarranm8odedreguysaaritaymendelerezbitjoshk2redigmayona007jonisarocombe

Keywords

bitcomponentscollaborationwebreactreact-componentsangularangular-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): teambit-owner is the consolidated org publisher for all @teambit/* packages; publisher change is an org-level transition, not a takeover. ai
maintainer-change maintainer-added AI (maintainer-change): learn-bit is part of the Teambit org; maintainer churn reflects org restructuring, not compromise. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of giteden/benjgil consistent with org-level consolidation to teambit-owner account. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): core-js is a known implicit/polyfill runtime dependency; phantom-dep false positive for this package. ai

Versions (showing 2 of 2)

Version Deps Published
0.0.503 2 / 7
0.0.502 2 / 7

v0.0.503

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

This version was published by a different npm account than previous versions on 2025-02-18. 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.502

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.