babel-plugin-styled-components
Improve the debugging experience and add server-side rendering support to styled-components
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:plckthn.me | AI (email-domain): Personal vanity domain lapse for a long-standing trusted maintainer (philplckthun). npm account auth is the real boundary; domain lapse is not a realistic attack vector here. | ai | |
| provenance | missing-githead | AI (provenance): Expected for publish environment change during 2018 maintainer transition; no security concern. | ai | |
| provenance | publisher-changed | AI (provenance): probablyup is a known styled-components maintainer; this is a legitimate team transition within the project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): probablyup and philpl are recognized styled-components contributors; legitimate maintainer update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): philplckthun removal coincides with philpl addition — likely username change or team reorganization. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; no-provenance is expected and stable for older versions. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 4 / 12 | |
| 2.2.0 | 4 / 12 | |
| 2.1.4 | 5 / 11 | |
| 2.1.3 | 5 / 11 | |
| 2.1.2 | 5 / 13 | |
| 2.1.1 | 5 / 13 | |
| 2.1.0 | 5 / 13 | |
| 2.0.7 | 5 / 13 | |
| 2.0.6 | 5 / 13 | |
| 2.0.5 | 5 / 13 | |
| 2.0.4 | 5 / 13 | |
| 2.0.3 | 5 / 13 | |
| 2.0.2 | 4 / 13 | |
| 2.0.1 | 4 / 13 | |
| 2.0.0 | 4 / 13 | |
| 1.13.3 | 4 / 13 | |
| 1.13.2 | 4 / 13 | |
| 1.13.1 | 4 / 13 | |
| 1.13.0 | 4 / 13 | |
| 1.12.1 | 4 / 13 | |
| 1.12.0 | 4 / 13 | |
| 1.11.1 | 4 / 12 | |
| 1.11.0 | 4 / 12 | |
| 1.10.7 | 4 / 12 | |
| 1.10.6 | 4 / 12 | |
| 1.10.5 | 4 / 12 | |
| 1.10.4 | 4 / 12 | |
| 1.10.3 | 4 / 12 | |
| 1.10.2 | 4 / 12 | |
| 1.10.1 | 4 / 12 | |
| 1.10.0 | 4 / 10 | |
| 1.9.4 | 3 / 9 | |
| 1.9.3 | 3 / 9 | |
| 1.9.2 | 3 / 9 | |
| 1.9.1 | 3 / 9 | |
| 1.9.0 | 3 / 9 | |
| 1.8.0 | 2 / 9 | |
| 1.7.2 | 3 / 9 | |
| 1.7.1 | 2 / 9 | |
| 1.7.0 | 1 / 9 | |
| 1.6.4 | 1 / 9 | |
| 1.6.3 | 1 / 9 | |
| 1.6.2 | 2 / 9 | |
| 1.6.1 | 2 / 9 | |
| 1.6.0 | 2 / 7 | |
| 1.5.1 | 3 / 4 | |
| 1.5.0 | 3 / 4 | |
| 1.4.0 | 2 / 4 | |
| 1.3.0 | 2 / 4 | |
| 1.2.1 | 2 / 3 | |
| 1.2.0 | 1 / 3 |
v2.3.0
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.10.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.10.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.10.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.10.1
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.7.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-09. This could indicate a legitimate maintainer transition or an account compromise.
v1.7.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-06. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.2
2 findingsThis version was published by a different npm account than previous versions on 2018-09-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
v1.6.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
This version was published by a different npm account than previous versions on 2018-08-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: probablyup.
This version was published by a different npm account than previous versions on 2018-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-22. This could indicate a legitimate maintainer transition or an account compromise.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-03. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
3 findingsMaintainer email '[email protected]' uses domain 'plckthn.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-08-29. This could indicate a legitimate maintainer transition or an account compromise.