inline-style-parser
An inline style parser.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.2.7 | 0 / 20 | |
| 0.2.6 | 0 / 20 | |
| 0.2.5 | 0 / 19 | |
| 0.2.4 | 0 / 17 | |
| 0.2.3 | 0 / 12 | |
| 0.2.2 | 0 / 13 | |
| 0.2.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.2 | 0 / 14 | |
| 0.1.1 | 0 / 14 | |
| 0.1.0 | 0 / 14 |
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.