@teambit/clear-cache
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/scope.objects | AI (dependencies): First-party @teambit monorepo package, consistent with prior versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are standard utilities/sibling monorepo package, consistent with Bit ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal teambit org maintainer rotation; no suspicious new publisher or code changes. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo internal package; description gap is stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse in npm; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal teambit monorepo sibling dependency; stable pattern across all @teambit/* packages. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.workspace-locator | AI (dependencies): Internal teambit monorepo sibling dependency. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): Internal teambit monorepo sibling dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Internal teambit monorepo sibling dependency. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.fs-cache | AI (dependencies): Internal teambit monorepo sibling dependency. | ai | |
| dependencies | unvetted-dep:@teambit/scope.modules.find-scope-path | AI (dependencies): Internal teambit monorepo sibling dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.0.568 | 7 / 3 | |
| 0.0.547 | 7 / 3 | |
| 0.0.546 | 7 / 3 | |
| 0.0.545 | 7 / 3 | |
| 0.0.544 | 7 / 3 | |
| 0.0.543 | 7 / 3 | |
| 0.0.542 | 7 / 3 | |
| 0.0.541 | 7 / 3 | |
| 0.0.540 | 7 / 3 | |
| 0.0.538 | 7 / 3 | |
| 0.0.534 | 8 / 3 | |
| 0.0.533 | 8 / 3 | |
| 0.0.515 | 8 / 3 | |
| 0.0.505 | 8 / 3 | |
| 0.0.481 | 8 / 3 | |
| 0.0.480 | 8 / 3 | |
| 0.0.473 | 8 / 3 | |
| 0.0.469 | 8 / 3 | |
| 0.0.426 | 10 / 3 | |
| 0.0.419 | 10 / 3 | |
| 0.0.410 | 5 / 4 | |
| 0.0.409 | 2 / 3 | |
| 0.0.408 | 2 / 3 |
v0.0.568
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.542
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.505
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.419
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.410
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.409
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.408
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.