@codingame/monaco-vscode-configuration-service-override
VSCode public API plugged on the monaco editor - configuration 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): CodinGame org migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this package going forward. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-158b9837-fc78-5d9c-86f5-9134e4358643-common | AI (dependencies): Internal @codingame scoped sibling package pinned to same version; part of the monaco-vscode-api monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-422642f2-7e3a-5c1c-9e1e-1d3ef1817346-common | AI (dependencies): Internal @codingame scoped sibling package pinned to same version; part of the monaco-vscode-api monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-d987325e-3e05-53aa-b9ff-6f97476f64db-common | AI (dependencies): Internal @codingame scoped sibling package pinned to same version; part of the monaco-vscode-api monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-f24e325c-2ce0-5bba-8236-bfc4f53180ab-common | AI (dependencies): Internal @codingame scoped sibling package pinned to same version; part of the monaco-vscode-api monorepo. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-ce7c734f-7712-563c-9335-d7acb43306af-common | AI (dependencies): Internal @codingame scoped sibling package pinned to same version; part of the monaco-vscode-api monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established CodinGame package with 273 published versions; provenance absence is consistent across the org. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 33.0.9 | 2 / 0 | |
| 33.0.8 | 2 / 0 | |
| 33.0.7 | 2 / 0 | |
| 33.0.6 | 2 / 0 | |
| 33.0.5 | 2 / 0 | |
| 33.0.4 | 2 / 0 | |
| 32.0.2 | 2 / 0 | |
| 32.0.1 | 2 / 0 | |
| 32.0.0 | 2 / 0 | |
| 31.0.1 | 2 / 0 | |
| 31.0.0 | 2 / 0 | |
| 30.0.1 | 2 / 0 | |
| 30.0.0 | 2 / 0 | |
| 29.1.1 | 2 / 0 | |
| 29.1.0 | 2 / 0 | |
| 29.0.0 | 2 / 0 | |
| 28.4.1 | 2 / 0 | |
| 28.4.0 | 2 / 0 | |
| 28.3.1 | 2 / 0 | |
| 28.3.0 | 2 / 0 | |
| 28.2.0 | 2 / 0 | |
| 28.1.2 | 2 / 0 | |
| 28.1.1 | 2 / 0 | |
| 28.0.1 | 2 / 0 | |
| 28.0.0 | 2 / 0 | |
| 27.0.0 | 2 / 0 | |
| 26.2.2 | 2 / 0 | |
| 26.2.1 | 2 / 0 | |
| 26.2.0 | 2 / 0 | |
| 26.1.2 | 2 / 0 | |
| 26.1.1 | 2 / 0 | |
| 26.1.0 | 2 / 0 | |
| 26.0.1 | 2 / 0 | |
| 26.0.0 | 2 / 0 | |
| 25.1.2 | 2 / 0 | |
| 25.1.1 | 2 / 0 | |
| 25.1.0 | 2 / 0 | |
| 25.0.1 | 2 / 0 | |
| 25.0.0 | 2 / 0 | |
| 24.3.0 | 2 / 0 | |
| 24.2.0 | 2 / 0 | |
| 24.1.1 | 2 / 0 | |
| 24.1.0 | 2 / 0 | |
| 23.3.0 | 7 / 0 | |
| 23.2.2 | 7 / 0 | |
| 23.2.1 | 7 / 0 | |
| 23.2.0 | 7 / 0 | |
| 23.1.1 | 7 / 0 | |
| 23.1.0 | 7 / 0 | |
| 23.0.4 | 7 / 0 | |
| 23.0.3 | 7 / 0 |
v33.0.9
1 findingPublished 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.4
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.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.