← Home

@teambit/lanes.ui.compare.lane-compare-page

npm Repository Homepage
11
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

teambit-ownershohamgiladdavidfirstlalybarranm8guysaaritaymendelerezbitjoshk2redigmayona007

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 publisher. ai
provenance no-provenance AI (provenance): Teambit packages do not use Sigstore provenance; consistent across all their releases. ai

Versions (showing 11 of 11)

Version Deps Published
0.0.174 3 / 2
0.0.173 3 / 2
0.0.172 3 / 2
0.0.171 3 / 2
0.0.170 3 / 2
0.0.169 3 / 2
0.0.168 3 / 2
0.0.167 3 / 2
0.0.166 3 / 2
0.0.165 3 / 2
0.0.164 3 / 2

v0.0.169

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: teambit-owner → shohamgilad (on 2025-02-09, known maintainer) provenance

This version was published by a different npm account (shohamgilad) than the most recent previously approved version (teambit-owner) on 2025-02-09, but shohamgilad is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.168

1 finding
INFO No provenance attestation provenance

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

v0.0.167

1 finding
INFO No provenance attestation provenance

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

v0.0.166

1 finding
INFO No provenance attestation provenance

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

v0.0.165

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.164

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.