@codingame/monaco-vscode-7559b0be-bfa5-5fe6-b731-1973fe9fffa1-common
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
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 16.1.1 | 2 / 0 | |
| 16.1.0 | 2 / 0 | |
| 16.0.6 | 2 / 0 | |
| 16.0.4 | 2 / 0 | |
| 16.0.3 | 2 / 0 | |
| 16.0.2 | 2 / 0 | |
| 16.0.1 | 2 / 0 | |
| 16.0.0 | 2 / 0 | |
| 15.0.3 | 2 / 0 |
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.