← Home

@teambit/lanes.ui.navigation.lane-switcher

npm Repository Homepage
8
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 publisher-changed AI (provenance): Publisher changed within teambit org (shohamgilad → teambit-owner); teambit-owner has 882 approved packages, consistent with org account consolidation. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal is part of the same teambit org account consolidation; no external actor involved. ai
npm-metadata no-description AI (npm-metadata): Teambit component packages consistently omit descriptions; stable false positive for this org. ai
provenance no-provenance AI (provenance): Teambit packages do not use Sigstore provenance; consistent across all their releases. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.239 8 / 3
0.0.238 8 / 3
0.0.237 8 / 3
0.0.236 8 / 3
0.0.235 8 / 3
0.0.234 7 / 3
0.0.233 7 / 3
0.0.232 7 / 3

v0.0.239

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.238

2 findings
HIGH Publisher changed: shohamgilad → teambit-owner (on 2025-12-01) provenance

This version was published by a different npm account than previous versions on 2025-12-01. 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.237

2 findings
HIGH Publisher changed: shohamgilad → teambit-owner (on 2025-11-27) provenance

This version was published by a different npm account than previous versions on 2025-11-27. 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.236

2 findings
HIGH Publisher changed: shohamgilad → teambit-owner (on 2025-11-09) provenance

This version was published by a different npm account than previous versions on 2025-11-09. 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.235

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

This version was published by a different npm account than previous versions on 2025-08-06. 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.234

1 finding
LOW No provenance attestation provenance

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

v0.0.233

1 finding
LOW No provenance attestation provenance

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

v0.0.232

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.