@codingame/monaco-vscode-8ccb7637-50ea-5359-97bf-00015d7fe567-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-16b9b017-9377-5198-9904-c344b3b2ad14-common | AI (dependencies): Same-publisher CodinGame sibling package; UUID naming is the established pattern for this monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-3b5a5cd1-d4ff-500a-b609-57e0cd4afa0a-common | AI (dependencies): Same-publisher CodinGame sibling package; UUID naming is the established pattern for this monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-4db3f2fb-d745-58fe-9e0e-eb67152ab711-common | AI (dependencies): Same-publisher CodinGame sibling package; UUID naming is the established pattern for this monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-6db1b967-5327-5c5c-8c17-bd92774c0fb2-common | AI (dependencies): Sibling package from same CodinGame org, pinned to same version; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-897bebad-39df-57cb-8a57-36a271d038be-common | AI (dependencies): Sibling package from same CodinGame org, pinned to same version; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-d941ac7b-412f-57e3-b1bf-f6b0eb253b21-common | AI (dependencies): Sibling package from same CodinGame org, pinned to same version; stable false positive for this package family. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 23.3.0 | 5 / 0 | |
| 23.2.2 | 5 / 0 | |
| 23.2.1 | 5 / 0 | |
| 23.2.0 | 5 / 0 | |
| 23.1.1 | 5 / 0 | |
| 23.1.0 | 5 / 0 | |
| 23.0.4 | 5 / 0 | |
| 23.0.3 | 5 / 0 | |
| 23.0.2 | 5 / 0 | |
| 23.0.1 | 5 / 0 | |
| 23.0.0 | 5 / 0 | |
| 22.1.9 | 5 / 0 | |
| 22.1.8 | 5 / 0 | |
| 22.1.7 | 5 / 0 | |
| 22.1.6 | 5 / 0 | |
| 22.1.5 | 5 / 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. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.