← Home

@teambit/workspace-config-files

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

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. ai
dependencies unvetted-dep:@teambit/bit-error AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. ai
dependencies unvetted-dep:@teambit/legacy.consumer AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. ai
dependencies unvetted-dep:@teambit/toolbox.path.path AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. ai
dependencies unvetted-dep:@teambit/toolbox.crypto.sha1 AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. 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 publishes without Sigstore provenance across all their packages; not a risk signal here. ai
phantom-deps phantom-dep:@teambit/toolbox.path.path AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is unreliable for bundled/compiled packages. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.990 17 / 5
1.0.972 17 / 5
1.0.971 17 / 5
1.0.970 17 / 5
1.0.968 17 / 5

v1.0.990

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

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

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

1 finding
LOW No provenance attestation provenance

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