gridstack
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): preinstall is `npx only-allow yarn` package-manager guard; benign and stable. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 13.1.2 | 0 / 35 | |
| 13.1.1 | 0 / 35 | |
| 13.1.0 | 0 / 35 | |
| 13.0.2 | 0 / 35 | |
| 13.0.1 | 0 / 35 | |
| 13.0.0 | 0 / 35 | |
| 12.6.0 | 0 / 35 | |
| 12.5.0 | 0 / 35 | |
| 12.4.2 | 0 / 35 | |
| 12.4.1 | 0 / 35 | |
| 12.4.0 | 0 / 35 | |
| 12.3.3 | 0 / 35 | |
| 12.3.2 | 0 / 34 | |
| 12.3.1 | 0 / 34 | |
| 12.3.0 | 0 / 34 | |
| 12.2.2 | 0 / 32 | |
| 12.2.1 | 0 / 32 | |
| 12.2.0 | 0 / 32 | |
| 12.1.2 | 0 / 32 | |
| 12.1.1 | 0 / 32 | |
| 12.1.0 | 0 / 32 | |
| 12.0.0 | 0 / 32 |
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
2 findingsScript: npx only-allow yarn
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.