style-to-js
Parses CSS inline style to JavaScript object (camelCased).
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher moved to GitHub Actions CI/CD with SLSA provenance; legitimate automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after dormancy with full SLSA provenance; normal for established packages. | ai | |
| dependencies | unvetted-dep:style-to-object | AI (dependencies): style-to-object is the well-known upstream CSS parser this package wraps; its use here is expected and benign for all versions of style-to-js. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 20 | |
| 1.1.21 | 1 / 23 | |
| 1.1.20 | 1 / 23 | |
| 1.1.19 | 1 / 23 | |
| 1.1.18 | 1 / 23 | |
| 1.1.17 | 1 / 23 | |
| 1.1.3 | 1 / 19 |
v2.0.0
2 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.