@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 100 of 222)
| Version | Deps | Published |
|---|---|---|
| 1.0.422 | 10 / 5 | |
| 1.0.421 | 10 / 5 | |
| 1.0.419 | 10 / 5 | |
| 1.0.416 | 10 / 5 | |
| 1.0.414 | 10 / 5 | |
| 1.0.413 | 10 / 5 | |
| 1.0.410 | 10 / 6 | |
| 1.0.408 | 10 / 6 | |
| 1.0.406 | 10 / 6 | |
| 1.0.404 | 10 / 6 | |
| 1.0.402 | 10 / 6 | |
| 1.0.400 | 10 / 6 | |
| 1.0.399 | 10 / 6 | |
| 1.0.396 | 10 / 6 | |
| 1.0.394 | 10 / 6 | |
| 1.0.392 | 10 / 6 | |
| 1.0.391 | 10 / 6 | |
| 1.0.389 | 10 / 6 | |
| 1.0.388 | 10 / 6 | |
| 1.0.385 | 10 / 6 | |
| 1.0.383 | 10 / 6 | |
| 1.0.382 | 10 / 6 | |
| 1.0.381 | 10 / 6 | |
| 1.0.380 | 10 / 6 | |
| 1.0.377 | 10 / 6 | |
| 1.0.376 | 10 / 6 | |
| 1.0.374 | 10 / 6 | |
| 1.0.372 | 10 / 6 | |
| 1.0.370 | 10 / 6 | |
| 1.0.366 | 10 / 6 | |
| 1.0.358 | 10 / 6 | |
| 1.0.356 | 10 / 6 | |
| 1.0.355 | 10 / 6 | |
| 1.0.353 | 10 / 6 | |
| 1.0.351 | 10 / 6 | |
| 1.0.349 | 10 / 6 | |
| 1.0.347 | 10 / 6 | |
| 1.0.345 | 10 / 6 | |
| 1.0.344 | 10 / 6 | |
| 1.0.342 | 10 / 6 | |
| 1.0.340 | 10 / 6 | |
| 1.0.339 | 10 / 6 | |
| 1.0.337 | 10 / 6 | |
| 1.0.335 | 10 / 6 | |
| 1.0.334 | 10 / 6 | |
| 1.0.333 | 10 / 6 | |
| 1.0.332 | 9 / 6 | |
| 1.0.331 | 9 / 6 | |
| 1.0.330 | 9 / 6 | |
| 1.0.329 | 9 / 6 | |
| 1.0.328 | 9 / 6 | |
| 1.0.327 | 9 / 6 | |
| 1.0.326 | 9 / 6 | |
| 1.0.325 | 9 / 6 | |
| 1.0.324 | 9 / 6 | |
| 1.0.323 | 9 / 6 | |
| 1.0.322 | 9 / 6 | |
| 1.0.321 | 9 / 6 | |
| 1.0.320 | 9 / 6 | |
| 1.0.319 | 9 / 6 | |
| 1.0.318 | 9 / 6 | |
| 1.0.317 | 9 / 6 | |
| 1.0.316 | 9 / 6 | |
| 1.0.315 | 9 / 6 | |
| 1.0.314 | 9 / 6 | |
| 1.0.313 | 9 / 6 | |
| 1.0.312 | 9 / 6 | |
| 1.0.311 | 9 / 6 | |
| 1.0.310 | 9 / 6 | |
| 1.0.309 | 9 / 6 | |
| 1.0.308 | 9 / 6 | |
| 1.0.307 | 9 / 6 | |
| 1.0.306 | 9 / 6 | |
| 1.0.305 | 9 / 6 | |
| 1.0.304 | 9 / 6 | |
| 1.0.303 | 9 / 6 | |
| 1.0.302 | 9 / 6 | |
| 1.0.301 | 9 / 6 | |
| 1.0.300 | 9 / 6 | |
| 1.0.299 | 9 / 6 | |
| 1.0.298 | 9 / 6 | |
| 1.0.297 | 9 / 6 | |
| 1.0.296 | 9 / 6 | |
| 1.0.295 | 9 / 6 | |
| 1.0.294 | 9 / 6 | |
| 1.0.293 | 9 / 6 | |
| 1.0.292 | 9 / 6 | |
| 1.0.291 | 9 / 6 | |
| 1.0.290 | 9 / 6 | |
| 1.0.289 | 9 / 6 | |
| 1.0.288 | 9 / 6 | |
| 1.0.287 | 9 / 6 | |
| 1.0.286 | 9 / 6 | |
| 1.0.285 | 9 / 6 | |
| 1.0.284 | 9 / 6 | |
| 1.0.283 | 9 / 6 | |
| 1.0.282 | 9 / 6 | |
| 1.0.281 | 9 / 6 | |
| 1.0.280 | 9 / 6 | |
| 1.0.279 | 9 / 6 |
v1.0.422
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.421
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.419
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.416
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.414
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.413
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.410
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.408
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.406
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.404
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.402
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.400
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.399
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.396
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.394
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.392
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.391
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.389
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.388
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.385
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.383
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.382
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.381
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.380
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.377
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.376
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.374
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.372
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.370
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.366
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.358
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.356
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.355
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.353
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.351
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.349
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.347
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.345
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.344
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.342
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.340
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.339
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.337
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.335
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.334
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.333
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.332
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.331
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.330
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.329
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.328
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.326
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.306
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.297
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.296
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.