@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 22 of 222)
| Version | Deps | Published |
|---|---|---|
| 1.0.278 | 9 / 6 | |
| 1.0.277 | 10 / 6 | |
| 1.0.276 | 10 / 6 | |
| 1.0.275 | 10 / 6 | |
| 1.0.274 | 10 / 6 | |
| 1.0.273 | 10 / 6 | |
| 1.0.272 | 10 / 6 | |
| 1.0.271 | 10 / 6 | |
| 1.0.270 | 10 / 6 | |
| 1.0.269 | 10 / 6 | |
| 1.0.268 | 10 / 6 | |
| 1.0.267 | 10 / 6 | |
| 1.0.266 | 10 / 6 | |
| 1.0.265 | 10 / 6 | |
| 1.0.264 | 10 / 6 | |
| 1.0.263 | 10 / 6 | |
| 1.0.262 | 10 / 6 | |
| 1.0.261 | 10 / 6 | |
| 1.0.260 | 10 / 6 | |
| 1.0.259 | 10 / 6 | |
| 1.0.258 | 10 / 6 | |
| 1.0.257 | 10 / 6 |
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
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 (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-02, 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.259
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 (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-01, 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.