@teambit/renaming
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* package from the same monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/envs | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/config | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/remove | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/graphql | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/install | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/compiler | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/component | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/deprecation | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/refactoring | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/legacy-bit-id | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/component-writer | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/new-component-helper | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.node-modules-linker | AI (dependencies): Sibling @teambit/* package from the same monorepo. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component package; missing description is a consistent pattern across all @teambit/* packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all @teambit/* releases; not a risk signal for this publisher. | ai |
Versions (showing 8 of 408)
| Version | Deps | Published |
|---|---|---|
| 1.0.617 | 23 / 7 | |
| 1.0.616 | 23 / 7 | |
| 1.0.615 | 23 / 7 | |
| 1.0.614 | 23 / 7 | |
| 1.0.613 | 23 / 7 | |
| 1.0.612 | 23 / 7 | |
| 1.0.611 | 23 / 7 | |
| 1.0.610 | 23 / 7 |
v1.0.617
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.616
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.615
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.614
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.613
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.612
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.611
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.