← Home

@teambit/deprecation

51
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/ui AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/cli AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/docs AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/scope AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/issues AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/graphql AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/component AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/workspace AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/component-id AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/component-issues AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/dependency-resolver AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
dependencies unvetted-dep:@teambit/component.ui.component-deprecated AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline gap, not a security risk. ai
npm-metadata no-description AI (npm-metadata): Monorepo component package; missing description is a cosmetic issue, not a security signal. ai
provenance no-provenance AI (provenance): Established teambit/bit monorepo; lack of provenance is common for this publisher. ai

Versions (showing 51 of 394)

View all versions
Version Deps Published
1.0.1007 17 / 4
1.0.1006 17 / 4
1.0.1005 17 / 4
1.0.1004 17 / 4
1.0.1003 17 / 4
1.0.1002 17 / 4
1.0.1001 17 / 4
1.0.1000 17 / 4
1.0.999 17 / 4
1.0.998 17 / 4
1.0.997 17 / 4
1.0.996 17 / 4
1.0.995 17 / 4
1.0.994 17 / 4
1.0.993 17 / 4
1.0.992 17 / 4
1.0.991 17 / 4
1.0.990 17 / 4
1.0.989 17 / 4
1.0.988 17 / 4
1.0.987 17 / 4
1.0.986 17 / 4
1.0.985 17 / 4
1.0.984 17 / 4
1.0.983 17 / 4
1.0.982 17 / 4
1.0.981 17 / 4
1.0.980 17 / 4
1.0.979 17 / 4
1.0.978 17 / 4
1.0.977 17 / 4
1.0.976 17 / 4
1.0.975 17 / 4
1.0.974 17 / 4
1.0.973 17 / 4
1.0.972 17 / 4
1.0.971 17 / 4
1.0.970 17 / 4
1.0.969 17 / 4
1.0.968 17 / 4
1.0.967 17 / 4
1.0.966 17 / 4
1.0.965 17 / 4
1.0.964 17 / 4
1.0.963 17 / 4
1.0.962 17 / 4
1.0.961 17 / 4
1.0.960 17 / 4
1.0.959 17 / 4
1.0.958 17 / 4
1.0.957 17 / 4

v1.0.1007

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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
INFO No provenance attestation provenance

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

v1.0.969

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

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

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

1 finding
INFO No provenance attestation provenance

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