@teambit/defender.eslint.config-mutator
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/defender.eslint-linter | AI (dependencies): Sibling package within the same teambit org; stable internal dependency across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is a long-standing teambit account with 206 approved packages; dormancy reflects component versioning cadence, not takeover risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped component package from teambit monorepo; missing description is a consistent pattern across their components, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): teambit publishes many packages without provenance; consistent across their ecosystem. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.123 | 2 / 5 | |
| 0.0.122 | 3 / 5 | |
| 0.0.121 | 3 / 5 | |
| 0.0.120 | 3 / 5 | |
| 0.0.119 | 3 / 5 | |
| 0.0.118 | 3 / 5 | |
| 0.0.117 | 3 / 5 | |
| 0.0.116 | 3 / 5 | |
| 0.0.115 | 3 / 5 | |
| 0.0.114 | 3 / 5 | |
| 0.0.113 | 3 / 5 | |
| 0.0.112 | 3 / 5 |
v0.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.