@teambit/tracker
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:firstline | AI (dependencies): Legitimate utility dep in established teambit/bit monorepo package. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/envs | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:array-difference | AI (dependencies): Legitimate utility dep in established teambit/bit monorepo package. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy-bit-id | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.analytics | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.node-modules-linker | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component; missing description is a cosmetic issue, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes 2000+ versions without provenance; consistent pattern, not a risk signal. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.972 | 23 / 4 | |
| 1.0.971 | 23 / 4 | |
| 1.0.970 | 23 / 4 | |
| 1.0.968 | 23 / 4 | |
| 1.0.955 | 23 / 4 |
v1.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.955
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.