@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, 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 |
|---|---|---|---|---|
| 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 100 of 203)
| Version | Deps | Published |
|---|---|---|
| 0.0.409 | 4 / 4 | |
| 0.0.408 | 4 / 4 | |
| 0.0.407 | 4 / 4 | |
| 0.0.406 | 4 / 4 | |
| 0.0.405 | 4 / 4 | |
| 0.0.404 | 4 / 4 | |
| 0.0.403 | 4 / 4 | |
| 0.0.402 | 4 / 4 | |
| 0.0.401 | 4 / 4 | |
| 0.0.400 | 4 / 4 | |
| 0.0.399 | 4 / 4 | |
| 0.0.398 | 4 / 4 | |
| 0.0.397 | 4 / 4 | |
| 0.0.396 | 4 / 4 | |
| 0.0.395 | 4 / 4 | |
| 0.0.394 | 4 / 4 | |
| 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 | |
| 0.0.310 | 4 / 4 | |
| 0.0.308 | 4 / 4 | |
| 0.0.307 | 4 / 4 |
v0.0.409
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.408
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.407
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.406
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.405
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.404
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.403
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.402
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.