@teambit/component.testing.mock-components
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): davidfirst is a long-standing teambit contributor with 178 approved packages; transition is legitimate. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): First-party teambit dependency; consistent with the package's org and ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.testing.load-aspect | AI (dependencies): First-party teambit dependency; consistent with the package's org and ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped component package from teambit; missing description is a cosmetic issue, not a risk signal. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 0.0.393 | 4 / 4 | |
| 0.0.392 | 4 / 4 | |
| 0.0.391 | 4 / 4 | |
| 0.0.390 | 4 / 4 | |
| 0.0.389 | 4 / 4 | |
| 0.0.388 | 4 / 4 | |
| 0.0.387 | 4 / 4 | |
| 0.0.386 | 4 / 4 | |
| 0.0.385 | 4 / 4 | |
| 0.0.384 | 4 / 4 | |
| 0.0.383 | 4 / 4 | |
| 0.0.382 | 4 / 4 | |
| 0.0.381 | 4 / 4 | |
| 0.0.380 | 4 / 4 | |
| 0.0.379 | 4 / 4 | |
| 0.0.378 | 4 / 4 | |
| 0.0.377 | 4 / 4 | |
| 0.0.376 | 4 / 4 | |
| 0.0.375 | 4 / 4 | |
| 0.0.374 | 4 / 4 | |
| 0.0.373 | 4 / 4 | |
| 0.0.372 | 4 / 4 | |
| 0.0.371 | 4 / 4 | |
| 0.0.370 | 4 / 4 | |
| 0.0.369 | 4 / 4 | |
| 0.0.368 | 4 / 4 | |
| 0.0.367 | 4 / 4 | |
| 0.0.366 | 4 / 4 | |
| 0.0.365 | 4 / 4 | |
| 0.0.364 | 4 / 4 | |
| 0.0.363 | 4 / 4 | |
| 0.0.362 | 4 / 4 | |
| 0.0.361 | 4 / 4 | |
| 0.0.360 | 4 / 4 | |
| 0.0.359 | 4 / 4 | |
| 0.0.358 | 4 / 4 | |
| 0.0.357 | 4 / 4 | |
| 0.0.356 | 4 / 4 | |
| 0.0.355 | 4 / 4 | |
| 0.0.354 | 4 / 4 | |
| 0.0.353 | 4 / 4 | |
| 0.0.352 | 4 / 4 | |
| 0.0.351 | 4 / 4 | |
| 0.0.350 | 4 / 4 | |
| 0.0.349 | 4 / 4 | |
| 0.0.348 | 4 / 4 | |
| 0.0.347 | 4 / 4 | |
| 0.0.346 | 4 / 4 | |
| 0.0.345 | 4 / 4 | |
| 0.0.344 | 4 / 4 | |
| 0.0.343 | 4 / 4 | |
| 0.0.342 | 4 / 4 | |
| 0.0.341 | 4 / 4 | |
| 0.0.340 | 4 / 4 | |
| 0.0.339 | 4 / 4 | |
| 0.0.338 | 4 / 4 | |
| 0.0.337 | 4 / 4 | |
| 0.0.336 | 4 / 4 | |
| 0.0.335 | 4 / 4 | |
| 0.0.334 | 4 / 4 | |
| 0.0.333 | 4 / 4 | |
| 0.0.332 | 4 / 4 | |
| 0.0.329 | 4 / 4 | |
| 0.0.328 | 4 / 4 | |
| 0.0.327 | 4 / 4 | |
| 0.0.326 | 4 / 4 | |
| 0.0.325 | 4 / 4 | |
| 0.0.324 | 4 / 4 | |
| 0.0.323 | 4 / 4 | |
| 0.0.322 | 4 / 4 | |
| 0.0.321 | 4 / 4 | |
| 0.0.320 | 4 / 4 | |
| 0.0.319 | 4 / 4 | |
| 0.0.318 | 4 / 4 | |
| 0.0.317 | 4 / 4 | |
| 0.0.316 | 4 / 4 | |
| 0.0.315 | 4 / 4 | |
| 0.0.314 | 4 / 4 | |
| 0.0.313 | 4 / 4 | |
| 0.0.312 | 4 / 4 | |
| 0.0.311 | 4 / 4 |
v0.0.393
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.392
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.391
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.390
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.389
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.388
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.387
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.386
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.385
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.384
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.383
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.382
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.381
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.378
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.377
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.375
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.374
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.373
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.371
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.370
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.369
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.368
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.367
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.366
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.365
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.364
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.363
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.362
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.361
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.360
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.359
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.358
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.357
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.356
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.355
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.354
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.353
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.352
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.351
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.350
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.349
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.348
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.347
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.346
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.345
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.344
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.343
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.341
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.340
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.339
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.338
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.337
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.336
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.335
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.334
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.333
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.332
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.329
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.328
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.327
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.326
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.324
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.323
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.322
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.321
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.320
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.319
2 findingsThis version was published by a different npm account than previous versions on 2025-07-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.318
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.317
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.313
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.