@codingame/monaco-vscode-language-detection-worker-service-override
VSCode public API plugged on the monaco editor - language-detection-worker 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 publisher is consistent with SLSA-attested CI/CD automation for this org's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established CodinGame monorepo publisher with 626 approved packages; dormancy consistent with normal release cadence gaps. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-eda30bac-0984-5b42-9362-c68996b85232-common | AI (dependencies): Internal CodinGame namespace dependency following the same versioning pattern; consistent with the rest of the package family. | ai | |
| dependencies | unvetted-dep:@vscode/vscode-languagedetection | AI (dependencies): Aliased to @codingame/vscode-languagedetection, a known CodinGame fork; consistent pattern across this package family. | ai | |
| provenance | no-provenance | AI (provenance): Long-established CodinGame package; provenance not used across their 272-version history. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 33.0.9 | 2 / 0 | |
| 33.0.7 | 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.0 | 2 / 0 | |
| 28.3.1 | 2 / 0 | |
| 28.0.1 | 2 / 0 | |
| 28.0.0 | 2 / 0 | |
| 25.1.1 | 2 / 0 | |
| 25.0.1 | 2 / 0 | |
| 25.0.0 | 2 / 0 | |
| 24.3.0 | 2 / 0 | |
| 24.1.0 | 2 / 0 | |
| 23.3.0 | 3 / 0 | |
| 23.2.1 | 3 / 0 | |
| 23.2.0 | 3 / 0 | |
| 23.1.1 | 3 / 0 | |
| 23.1.0 | 3 / 0 | |
| 23.0.4 | 3 / 0 | |
| 23.0.3 | 3 / 0 | |
| 23.0.2 | 3 / 0 | |
| 23.0.1 | 3 / 0 | |
| 23.0.0 | 3 / 0 | |
| 22.1.9 | 3 / 0 | |
| 22.1.8 | 3 / 0 | |
| 22.1.7 | 3 / 0 | |
| 22.1.6 | 3 / 0 | |
| 22.1.5 | 3 / 0 | |
| 22.1.4 | 3 / 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.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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.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.
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.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.3.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.
v28.0.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.
v28.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.
v25.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.
v25.0.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.
v25.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.
v24.3.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.
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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.
v23.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.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.
v23.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.
v22.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.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.