@primer/styled-react
> A temporary package that bridges the gap between Primer React and styled-components
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): 102 new files consistent with new monorepo sub-package initial release, not injected code. | ai | |
| provenance | publisher-changed | AI (provenance): Primer org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated release. | ai | |
| source-diff | source-size-tripled | AI (source-diff): New sub-package bootstrapped from monorepo; size increase reflects initial full source, not injected payload. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Primer org consolidated publishing under GitHub Actions; individual maintainer accounts replaced by CI automation. | ai | |
| dependencies | unvetted-dep:@types/styled-system__theme-get | AI (dependencies): TypeScript type-only package; no runtime risk for this Primer org library. | ai | |
| dependencies | unvetted-dep:@types/styled-system__css | AI (dependencies): TypeScript type-only package; no runtime risk for this Primer org library. | ai | |
| phantom-deps | phantom-dep:@types/styled-system__css | AI (phantom-deps): Framework-scoped @types package loaded by convention, not direct import; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@styled-system/props | AI (phantom-deps): Declared in dependencies and used via styled-system ecosystem; phantom-dep heuristic FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/styled-system | AI (phantom-deps): Framework-scoped @types package loaded by convention; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/styled-system__theme-get | AI (phantom-deps): Framework-scoped @types package loaded by convention; stable FP for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 10 / 22 | |
| 1.0.9 | 10 / 22 | |
| 1.0.8 | 10 / 22 | |
| 1.0.7 | 10 / 22 | |
| 1.0.6 | 10 / 22 | |
| 1.0.5 | 10 / 22 | |
| 1.0.4 | 7 / 22 | |
| 1.0.3 | 7 / 22 | |
| 1.0.2 | 7 / 17 | |
| 1.0.1 | 7 / 17 | |
| 1.0.0 | 0 / 12 | |
| 0.4.0 | 7 / 17 | |
| 0.3.1 | 7 / 17 | |
| 0.3.0 | 7 / 17 |
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.