@teambit/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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Adds first-party @teambit sibling package, normal for this monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Teambit org package with strong publisher track record; maintainer cleanup is routine for this project. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit ecosystem dependency; stable pattern across all @teambit/* packages. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal @teambit ecosystem dependency; stable pattern across all @teambit/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit monorepo component packages consistently omit descriptions; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance; consistent across all 1609 versions. | ai |
Versions (showing 20 of 220)
| Version | Deps | Published |
|---|---|---|
| 0.0.975 | 4 / 7 | |
| 0.0.974 | 4 / 7 | |
| 0.0.973 | 4 / 7 | |
| 0.0.972 | 4 / 7 | |
| 0.0.971 | 4 / 7 | |
| 0.0.970 | 4 / 7 | |
| 0.0.969 | 4 / 7 | |
| 0.0.968 | 4 / 7 | |
| 0.0.967 | 4 / 7 | |
| 0.0.966 | 4 / 7 | |
| 0.0.965 | 4 / 7 | |
| 0.0.964 | 4 / 7 | |
| 0.0.963 | 4 / 7 | |
| 0.0.962 | 4 / 7 | |
| 0.0.961 | 4 / 7 | |
| 0.0.960 | 4 / 7 | |
| 0.0.959 | 4 / 7 | |
| 0.0.958 | 4 / 7 | |
| 0.0.957 | 4 / 7 | |
| 0.0.956 | 4 / 7 |
v0.0.975
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.974
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.973
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.968
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.967
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.966
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.965
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.964
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.963
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.962
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.961
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.960
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.959
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.958
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.957
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.956
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.