@codingame/monaco-vscode-1cb11a73-359e-5a2f-9e95-6989cc9858ee-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@codingame/monaco-vscode-4372ad43-a220-5e78-83e6-95a9cfd64384-common | AI (dependencies): Sibling generated package from same monorepo/build, not an external dependency. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-f5d4b045-44e8-55a8-b683-308656a412fa-common | AI (dependencies): Sibling generated package from same monorepo/build, not an external dependency. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Normal churn from monaco-vscode-api's auto-generated per-feature package splitting. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 18.4.0 | 4 / 0 | |
| 18.0.1 | 4 / 0 | |
| 18.0.0 | 4 / 0 | |
| 17.2.1 | 4 / 0 |
v18.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.