@codingame/monaco-vscode-theme-service-override
VSCode public API plugged on the monaco editor - theme 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@codingame/monaco-vscode-10416640-ca84-5eff-95ce-dea977ccba7a-common | AI (dependencies): Internal monorepo chunk dep from the same CodinGame publisher; UUID naming is a known pattern for this package family. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-9d0168a3-519b-57f3-9bcc-89efc41f951a-common | AI (dependencies): Internal monorepo chunk dep from the same CodinGame publisher; UUID naming is a known pattern for this package family. | ai | |
| provenance | no-provenance | AI (provenance): CodinGame consistently publishes without provenance; stable pattern across 132 approved packages. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 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 | 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 | |
| 22.1.4 | 5 / 0 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.1
1 findingPackage 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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.