← Home

@teambit/compositions.ui.composition-compare

npm Repository Homepage
6
Versions
Apache-2.0
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
phantom-deps phantom-dep:core-js AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package. ai
phantom-deps phantom-dep:@teambit/ui-foundation.ui.constants.z-indexes AI (phantom-deps): Same-org @teambit scope dependency; phantom-dep heuristic unreliable for Bit component packages. ai
npm-metadata no-description AI (npm-metadata): Established teambit component package; missing description is a consistent pattern across their component library, not a malware signal. ai

Versions (showing 6 of 6)

Version Deps Published
0.0.265 16 / 10
0.0.264 16 / 10
0.0.263 16 / 10
0.0.262 16 / 10
0.0.261 16 / 10
0.0.260 16 / 10

v0.0.265

1 finding
LOW No provenance attestation provenance

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

v0.0.264

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.

v0.0.263

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.

v0.0.262

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.

v0.0.261

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.

v0.0.260

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.