@codingame/monaco-vscode-debug-service-override
VSCode public API plugged on the monaco editor - debug service-override
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; stable pattern for this package going forward. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-262ed59d-4f76-57cd-9e9f-1877f26ae049-common | AI (dependencies): Internal CodinGame monaco-vscode-api sub-package; UUID naming is the project's established pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-3b5a5cd1-d4ff-500a-b609-57e0cd4afa0a-common | AI (dependencies): Internal CodinGame monaco-vscode-api sub-package; UUID naming is the project's established pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-afb6e5ca-fe46-5d5a-aa9c-f722ebefae39-common | AI (dependencies): Internal CodinGame monaco-vscode-api sub-package; UUID naming is the project's established pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-60014c9d-b815-501d-83a9-4b08725c2ec2-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-88aa9a78-75f5-5aaa-89e9-bbdd580b3b5c-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-a17e9d37-b6c1-5556-8402-5db73960fae3-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-a8d3bd74-e63e-5327-96e8-4f931661e329-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-ab07af84-42e8-5a0f-8aef-b83fb90ede21-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-ce7c734f-7712-563c-9335-d7acb43306af-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-d941ac7b-412f-57e3-b1bf-f6b0eb253b21-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-e39a1c8f-7892-5d9b-9987-7b10b79e1a0a-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-e59ecb8c-db32-5324-8fe4-cf9921fd92b8-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-f24e325c-2ce0-5bba-8236-bfc4f53180ab-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-b99aef83-0d60-5e8c-a62e-9908b6256f35-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-09e9b2e8-42a8-5a68-864f-bfcdad0ca1df-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-4bf376c2-03c7-58cb-8303-c67aeefa3d3d-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-501b06ab-3f58-516b-8a1a-c29d375d3da4-common | AI (dependencies): Internal monorepo sub-package; UUID naming is a known pattern for this CodinGame project. | ai | |
| provenance | no-provenance | AI (provenance): Established CodinGame package family; provenance absence is consistent across all their releases. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 33.0.9 | 1 / 0 | |
| 33.0.8 | 1 / 0 | |
| 33.0.7 | 1 / 0 | |
| 33.0.6 | 1 / 0 | |
| 33.0.5 | 1 / 0 | |
| 33.0.4 | 1 / 0 | |
| 32.0.2 | 1 / 0 | |
| 32.0.1 | 1 / 0 | |
| 32.0.0 | 1 / 0 | |
| 31.0.1 | 1 / 0 | |
| 31.0.0 | 1 / 0 | |
| 30.0.1 | 1 / 0 | |
| 30.0.0 | 1 / 0 | |
| 29.1.1 | 1 / 0 | |
| 29.1.0 | 1 / 0 | |
| 29.0.0 | 1 / 0 | |
| 28.4.1 | 1 / 0 | |
| 28.4.0 | 1 / 0 | |
| 28.3.1 | 1 / 0 | |
| 28.3.0 | 1 / 0 | |
| 28.2.0 | 1 / 0 | |
| 28.1.2 | 1 / 0 | |
| 28.1.1 | 1 / 0 | |
| 28.0.1 | 1 / 0 | |
| 28.0.0 | 1 / 0 | |
| 27.0.0 | 1 / 0 | |
| 26.2.2 | 1 / 0 | |
| 26.2.1 | 1 / 0 | |
| 26.2.0 | 1 / 0 | |
| 26.1.2 | 1 / 0 | |
| 26.1.1 | 1 / 0 | |
| 26.1.0 | 1 / 0 | |
| 26.0.1 | 1 / 0 | |
| 26.0.0 | 1 / 0 | |
| 25.1.2 | 1 / 0 | |
| 25.1.1 | 1 / 0 | |
| 25.1.0 | 1 / 0 | |
| 25.0.1 | 1 / 0 | |
| 25.0.0 | 1 / 0 | |
| 24.3.0 | 1 / 0 | |
| 24.2.0 | 1 / 0 | |
| 24.1.1 | 1 / 0 | |
| 24.1.0 | 1 / 0 | |
| 23.3.0 | 13 / 0 | |
| 23.2.2 | 13 / 0 | |
| 23.2.1 | 13 / 0 | |
| 23.2.0 | 13 / 0 | |
| 23.1.1 | 13 / 0 | |
| 23.1.0 | 14 / 0 | |
| 23.0.4 | 14 / 0 | |
| 23.0.3 | 14 / 0 |
v33.0.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.8
2 findingsThis version was published by a different npm account than previous versions on 2026-05-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-05-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v32.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.