@teambit/dev-files
Supply chain provenance
Status for the latest visible version.
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
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): Known maintainer manual publish per provenance record; not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org internal dependency addition, typical for this monorepo's release pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI releases; rapid successive publishes are normal for this org across 3200+ versions. | ai | |
| dependencies | unvetted-dep:@teambit/graphql | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/component | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| phantom-deps | phantom-dep:@teambit/component.sources | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive in Bit's component-based architecture. | ai | |
| provenance | no-provenance | AI (provenance): Established Bit monorepo package; lack of provenance is consistent across all 2825 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Bit core aspects consistently omit npm descriptions; homepage and componentId fields provide context. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/envs | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai | |
| dependencies | unvetted-dep:@teambit/scope | AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. | ai |
Versions (showing 51 of 222)
| Version | Deps | Published |
|---|---|---|
| 1.0.1060 | 11 / 4 | |
| 1.0.1056 | 11 / 4 | |
| 1.0.1055 | 11 / 4 | |
| 1.0.1054 | 11 / 4 | |
| 1.0.1052 | 11 / 4 | |
| 1.0.1051 | 11 / 4 | |
| 1.0.1021 | 11 / 4 | |
| 1.0.996 | 11 / 4 | |
| 1.0.981 | 11 / 4 | |
| 1.0.978 | 11 / 4 | |
| 1.0.976 | 11 / 4 | |
| 1.0.972 | 11 / 4 | |
| 1.0.971 | 11 / 4 | |
| 1.0.970 | 11 / 4 | |
| 1.0.969 | 11 / 4 | |
| 1.0.968 | 11 / 4 | |
| 1.0.966 | 11 / 4 | |
| 1.0.963 | 11 / 4 | |
| 1.0.957 | 11 / 4 | |
| 1.0.956 | 11 / 4 | |
| 1.0.955 | 11 / 4 | |
| 1.0.951 | 11 / 4 | |
| 1.0.950 | 11 / 4 | |
| 1.0.946 | 11 / 4 | |
| 1.0.945 | 11 / 4 | |
| 1.0.944 | 11 / 4 | |
| 1.0.943 | 11 / 4 | |
| 1.0.942 | 11 / 4 | |
| 1.0.941 | 11 / 4 | |
| 1.0.940 | 11 / 4 | |
| 1.0.939 | 11 / 4 | |
| 1.0.938 | 11 / 4 | |
| 1.0.937 | 11 / 4 | |
| 1.0.936 | 11 / 4 | |
| 1.0.935 | 11 / 4 | |
| 1.0.933 | 11 / 4 | |
| 1.0.932 | 11 / 4 | |
| 1.0.931 | 11 / 4 | |
| 1.0.930 | 11 / 4 | |
| 1.0.929 | 11 / 4 | |
| 1.0.928 | 11 / 4 | |
| 1.0.927 | 11 / 4 | |
| 1.0.926 | 11 / 4 | |
| 1.0.925 | 11 / 4 | |
| 1.0.911 | 11 / 4 | |
| 1.0.898 | 11 / 4 | |
| 1.0.821 | 11 / 4 | |
| 1.0.573 | 11 / 4 | |
| 1.0.553 | 11 / 4 | |
| 1.0.552 | 11 / 4 | |
| 1.0.551 | 11 / 4 |
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1054
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1052
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1051
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.981
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.978
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.821
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-11-25, but teambit-owner 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.573
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.553
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.552
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.551
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.