@teambit/forking
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Established teambit org package; maintainer rotation within the org is expected and not indicative of takeover. | ai | |
| 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/component-id | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-version | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-package-version | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit monorepo packages consistently omit descriptions; stable false positive for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance; consistent across all versions. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.0.995 | 24 / 4 | |
| 1.0.993 | 24 / 4 | |
| 1.0.992 | 24 / 4 | |
| 1.0.991 | 24 / 4 | |
| 1.0.990 | 24 / 4 | |
| 1.0.989 | 24 / 4 | |
| 1.0.988 | 24 / 4 | |
| 1.0.987 | 24 / 4 | |
| 1.0.986 | 24 / 4 | |
| 1.0.985 | 24 / 4 | |
| 1.0.983 | 24 / 4 | |
| 1.0.982 | 24 / 4 | |
| 1.0.979 | 24 / 4 | |
| 1.0.976 | 24 / 4 | |
| 1.0.975 | 24 / 4 | |
| 1.0.974 | 24 / 4 | |
| 1.0.973 | 24 / 4 | |
| 1.0.972 | 24 / 4 | |
| 1.0.971 | 24 / 4 | |
| 1.0.970 | 24 / 4 | |
| 1.0.969 | 24 / 4 | |
| 1.0.968 | 24 / 4 | |
| 1.0.963 | 24 / 4 | |
| 1.0.962 | 24 / 4 | |
| 1.0.958 | 24 / 4 | |
| 1.0.954 | 24 / 4 | |
| 1.0.950 | 24 / 4 | |
| 1.0.949 | 24 / 4 | |
| 1.0.943 | 24 / 4 | |
| 1.0.934 | 24 / 4 | |
| 1.0.926 | 24 / 4 | |
| 1.0.925 | 24 / 4 | |
| 1.0.798 | 23 / 4 | |
| 1.0.797 | 23 / 4 | |
| 1.0.643 | 23 / 4 | |
| 1.0.635 | 23 / 4 | |
| 1.0.632 | 23 / 4 | |
| 1.0.619 | 23 / 4 | |
| 1.0.618 | 23 / 4 | |
| 1.0.613 | 23 / 4 | |
| 1.0.612 | 23 / 4 | |
| 1.0.611 | 23 / 4 | |
| 1.0.610 | 23 / 4 |
v1.0.995
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.993
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.992
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.991
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.990
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.989
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.988
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.987
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.986
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.985
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.983
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.982
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.979
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.976
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.975
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.974
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.973
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.798
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.797
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.643
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.635
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.632
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.619
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.618
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.613
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.612
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.611
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.