@teambit/config-store
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): teambit-owner is the canonical publisher with strong track record; learn-bit removal appears to be routine org maintenance. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party @teambit dependency from the same publisher ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/gitconfig | AI (dependencies): First-party @teambit dependency from the same publisher ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): First-party @teambit dependency from the same publisher ecosystem; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Bit component packages routinely omit descriptions; stable pattern across this publisher's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this publisher's large component library; not a risk indicator here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.0.208 | 8 / 3 | |
| 0.0.207 | 8 / 3 | |
| 0.0.206 | 8 / 3 | |
| 0.0.205 | 8 / 3 | |
| 0.0.204 | 8 / 3 | |
| 0.0.202 | 8 / 3 | |
| 0.0.200 | 8 / 3 | |
| 0.0.199 | 8 / 3 | |
| 0.0.195 | 8 / 3 | |
| 0.0.192 | 8 / 3 | |
| 0.0.190 | 8 / 3 | |
| 0.0.189 | 8 / 3 | |
| 0.0.188 | 8 / 3 | |
| 0.0.187 | 8 / 3 | |
| 0.0.164 | 8 / 3 | |
| 0.0.99 | 8 / 3 | |
| 0.0.92 | 8 / 3 | |
| 0.0.91 | 8 / 3 | |
| 0.0.90 | 8 / 3 | |
| 0.0.89 | 8 / 3 | |
| 0.0.87 | 8 / 3 | |
| 0.0.84 | 8 / 3 | |
| 0.0.78 | 8 / 3 | |
| 0.0.76 | 8 / 3 | |
| 0.0.75 | 8 / 3 | |
| 0.0.74 | 8 / 3 | |
| 0.0.73 | 8 / 3 | |
| 0.0.72 | 8 / 3 | |
| 0.0.70 | 8 / 3 | |
| 0.0.69 | 8 / 3 | |
| 0.0.68 | 8 / 3 |
v0.0.208
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.202
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.189
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.188
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.164
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.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.