@ndla/styled-system
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:es/css/css.mjs | AI (source-diff): Minified PandaCSS build output; long lines are CSS utility mappings, not obfuscation. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.0.51 | 0 / 1 | |
| 0.0.49 | 0 / 1 | |
| 0.0.48 | 0 / 1 | |
| 0.0.47 | 0 / 1 | |
| 0.0.46 | 0 / 1 | |
| 0.0.44 | 0 / 1 | |
| 0.0.43 | 0 / 1 | |
| 0.0.42 | 0 / 1 | |
| 0.0.41 | 0 / 1 | |
| 0.0.40 | 0 / 1 | |
| 0.0.37 | 0 / 1 | |
| 0.0.36 | 0 / 1 | |
| 0.0.35 | 0 / 1 | |
| 0.0.34 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 |
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.