@dr.pogodin/babel-plugin-react-css-modules
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CircleCI CI publisher for established dr.pogodin package; legitimate automation. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped babel dep loaded by convention, not directly imported. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/traverse is an official, well-known Babel package. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 7.0.7 | 13 / 21 | |
| 7.0.6 | 13 / 21 | |
| 7.0.5 | 13 / 21 | |
| 7.0.4 | 13 / 21 | |
| 7.0.3 | 13 / 21 | |
| 7.0.2 | 13 / 21 | |
| 7.0.1 | 13 / 21 | |
| 7.0.0 | 13 / 20 | |
| 6.13.9 | 12 / 18 | |
| 6.13.8 | 12 / 18 | |
| 6.13.7 | 12 / 18 | |
| 6.13.6 | 12 / 22 | |
| 6.13.5 | 12 / 25 | |
| 6.13.4 | 12 / 25 | |
| 6.13.3 | 12 / 25 | |
| 6.13.2 | 12 / 24 | |
| 6.13.1 | 12 / 24 | |
| 6.13.0 | 12 / 24 | |
| 6.12.0 | 12 / 24 | |
| 6.11.0 | 12 / 24 | |
| 6.10.0 | 12 / 24 | |
| 6.9.4 | 11 / 25 | |
| 6.9.3 | 11 / 25 | |
| 6.9.2 | 11 / 25 | |
| 6.9.1 | 11 / 25 | |
| 6.9.0 | 11 / 25 | |
| 6.8.2 | 11 / 25 | |
| 6.8.0 | 11 / 25 | |
| 6.7.0 | 11 / 25 | |
| 6.6.1 | 11 / 25 | |
| 6.6.0 | 11 / 25 | |
| 6.5.4 | 11 / 25 | |
| 6.5.3 | 11 / 20 | |
| 6.5.2 | 11 / 20 | |
| 6.5.1 | 11 / 20 |
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-07-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.