@codingame/monaco-vscode-f6ab89b2-83b0-5a43-8772-cb0eafa650b5-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 — the axios compromise (March 2026) relied on exactly this gap.
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-45e04ac3-b807-5ae5-8818-7b9c40b6d31f-common | AI (dependencies): Sibling package from same CodinGame monorepo; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-88141f48-1af9-57ef-a278-f4b2ff6128fa-common | AI (dependencies): Sibling package from same CodinGame monorepo; not an independent third-party risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 23.3.0 | 4 / 0 | |
| 23.2.2 | 4 / 0 | |
| 23.2.1 | 4 / 0 | |
| 23.2.0 | 4 / 0 | |
| 23.1.1 | 4 / 0 | |
| 23.1.0 | 4 / 0 | |
| 23.0.4 | 4 / 0 | |
| 23.0.3 | 4 / 0 | |
| 23.0.2 | 4 / 0 | |
| 23.0.1 | 4 / 0 | |
| 23.0.0 | 4 / 0 |
v23.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.