@types/styled-components
TypeScript definitions for styled-components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type definitions are conventionally loaded; legitimate for styled-components type stubs. | ai | |
| phantom-deps | phantom-dep:@types/react-native | AI (phantom-deps): Framework-scoped type definitions are conventionally loaded; legitimate for styled-components type stubs. | ai | |
| phantom-deps | phantom-dep:@types/hoist-non-react-statics | AI (phantom-deps): Framework-scoped type definitions are conventionally loaded; legitimate for styled-components type stubs. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 5.1.36 | 3 / 0 | |
| 5.1.35 | 3 / 0 | |
| 5.1.34 | 3 / 0 | |
| 5.1.33 | 3 / 0 | |
| 5.1.32 | 3 / 0 | |
| 5.1.31 | 3 / 0 | |
| 5.1.30 | 3 / 0 | |
| 5.1.29 | 3 / 0 | |
| 5.1.28 | 3 / 0 | |
| 5.1.27 | 3 / 0 | |
| 5.1.26 | 3 / 0 | |
| 5.1.25 | 3 / 0 | |
| 5.1.24 | 3 / 0 | |
| 5.1.23 | 3 / 0 | |
| 5.1.22 | 3 / 0 | |
| 5.1.21 | 3 / 0 | |
| 5.1.20 | 3 / 0 | |
| 5.1.19 | 3 / 0 | |
| 5.1.18 | 3 / 0 | |
| 5.1.17 | 3 / 0 | |
| 5.1.16 | 3 / 0 | |
| 5.1.15 | 3 / 0 | |
| 5.1.14 | 3 / 0 | |
| 5.1.13 | 3 / 0 | |
| 5.1.12 | 3 / 0 | |
| 5.1.11 | 3 / 0 | |
| 5.1.10 | 3 / 0 | |
| 5.1.9 | 3 / 0 | |
| 5.1.8 | 3 / 0 | |
| 5.1.7 | 3 / 0 | |
| 5.1.6 | 4 / 0 | |
| 5.1.5 | 4 / 0 | |
| 5.1.4 | 4 / 0 | |
| 5.1.3 | 4 / 0 | |
| 5.1.2 | 4 / 0 | |
| 5.1.1 | 4 / 0 | |
| 5.1.0 | 4 / 0 | |
| 5.0.1 | 4 / 0 | |
| 5.0.0 | 4 / 0 | |
| 4.4.3 | 4 / 0 | |
| 4.4.2 | 4 / 0 | |
| 4.4.1 | 4 / 0 | |
| 4.4.0 | 3 / 0 | |
| 4.1.22 | 3 / 0 | |
| 4.1.21 | 3 / 0 | |
| 4.1.20 | 3 / 0 | |
| 4.1.19 | 3 / 0 | |
| 4.1.18 | 3 / 0 | |
| 4.1.17 | 3 / 0 | |
| 4.1.16 | 3 / 0 | |
| 4.1.15 | 3 / 0 |
v5.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.