← Home

@teambit/update-dependencies

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

Maintainers

learn-bitteambit-ownershohamgiladdavidfirstlalybarranm8odedreguysaaritaymendelerezbitjoshk2redigmayona007jonisarocombe

Keywords

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@teambit/scope.objects AI (dependencies): First-party teambit monorepo sibling package, not a third-party dependency. ai
npm-metadata no-description AI (npm-metadata): Established scoped package; missing description is stable pattern. ai
provenance no-provenance AI (provenance): Long-established package; provenance adoption is a future improvement, not a blocker. ai
publish-pattern new-deps-added AI (publish-pattern): First-party @teambit scoped dependency, standard monorepo pattern. ai
dependencies unvetted-dep:@teambit/legacy.constants AI (dependencies): First-party teambit monorepo split package. ai
publish-pattern dormant-publish AI (publish-pattern): Artifact of diff baseline being an old sibling version, not real inactivity. ai
dependencies unvetted-dep:@teambit/legacy.extension-data AI (dependencies): First-party teambit monorepo split package. ai
dependencies unvetted-dep:@teambit/legacy.consumer-component AI (dependencies): First-party teambit monorepo split package. ai
dependencies unvetted-dep:@teambit/pkg.modules.semver-helper AI (dependencies): First-party teambit monorepo split package. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.581 21 / 3
1.0.512 21 / 3
1.0.496 21 / 3
1.0.485 18 / 3
1.0.410 17 / 4
1.0.409 17 / 4
1.0.379 17 / 4
1.0.370 17 / 4
1.0.339 17 / 4
1.0.334 17 / 4
1.0.258 16 / 4

v1.0.581

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: shohamgilad → davidfirst (on 2025-03-28, known maintainer) provenance

This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2025-03-28, but davidfirst 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.

v1.0.512

1 finding
INFO No provenance attestation provenance

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

v1.0.496

1 finding
INFO No provenance attestation provenance

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

v1.0.485

1 finding
INFO No provenance attestation provenance

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

v1.0.410

1 finding
INFO No provenance attestation provenance

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

v1.0.409

1 finding
INFO No provenance attestation provenance

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

v1.0.379

1 finding
LOW No provenance attestation provenance

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

v1.0.370

1 finding
LOW No provenance attestation provenance

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

v1.0.339

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: shohamgilad → davidfirst (on 2024-07-17, known maintainer) provenance

This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-07-17, but davidfirst 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.

v1.0.334

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: shohamgilad → davidfirst (on 2024-07-13, known maintainer) provenance

This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-07-13, but davidfirst 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.

v1.0.258

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.