@codingame/monaco-vscode-terminal-service-override
VSCode public API plugged on the monaco editor - terminal 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-45e04ac3-b807-5ae5-8818-7b9c40b6d31f-common | AI (dependencies): Internal codingame monorepo sub-package; same versioned pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-2c64d2c2-fdf7-5675-a2fe-f6f65fbdedbf-common | AI (dependencies): Internal codingame monorepo sub-package; same versioned pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-09e9b2e8-42a8-5a68-864f-bfcdad0ca1df-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-422642f2-7e3a-5c1c-9e1e-1d3ef1817346-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-45a408c6-90ed-5d8b-801d-f3f69c7a97f2-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-625898ab-0e33-5b7f-a3ae-29c10271dc1c-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-88141f48-1af9-57ef-a278-f4b2ff6128fa-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-9ed6fe06-a052-57c2-a234-5d9b94d2e7e0-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-d26a96d3-122c-5a3d-a04d-deb5ff0f19c0-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-f6ab89b2-83b0-5a43-8772-cb0eafa650b5-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-72a1b7d3-3f58-5545-9b7e-f579bd003081-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-07eaa805-9dea-5ec6-a422-a4f04872424d-common | AI (dependencies): Internal monorepo sub-package from the same CodinGame publisher; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-xterm-common | AI (dependencies): Same-org monorepo sibling dependency pinned to matching version; stable pattern across all releases. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-xterm-addons-common | AI (dependencies): Same-org monorepo sibling dependency pinned to matching version; stable pattern across all releases. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 32.0.2 | 3 / 0 | |
| 32.0.1 | 3 / 0 | |
| 32.0.0 | 3 / 0 | |
| 31.0.1 | 3 / 0 | |
| 31.0.0 | 3 / 0 | |
| 30.0.1 | 3 / 0 | |
| 30.0.0 | 3 / 0 | |
| 29.1.1 | 3 / 0 | |
| 29.1.0 | 3 / 0 | |
| 29.0.0 | 3 / 0 | |
| 28.4.1 | 3 / 0 | |
| 28.4.0 | 3 / 0 | |
| 28.3.1 | 3 / 0 | |
| 28.3.0 | 3 / 0 | |
| 28.2.0 | 3 / 0 | |
| 28.1.2 | 3 / 0 | |
| 28.1.1 | 3 / 0 | |
| 28.0.1 | 3 / 0 | |
| 28.0.0 | 3 / 0 | |
| 27.0.0 | 3 / 0 | |
| 26.2.2 | 3 / 0 | |
| 26.2.1 | 3 / 0 | |
| 26.2.0 | 3 / 0 | |
| 26.1.2 | 3 / 0 | |
| 26.1.1 | 3 / 0 | |
| 26.1.0 | 3 / 0 | |
| 26.0.1 | 3 / 0 | |
| 26.0.0 | 3 / 0 | |
| 25.1.2 | 3 / 0 | |
| 25.1.1 | 3 / 0 | |
| 25.1.0 | 3 / 0 | |
| 25.0.1 | 3 / 0 | |
| 25.0.0 | 3 / 0 | |
| 24.3.0 | 3 / 0 | |
| 24.2.0 | 3 / 0 | |
| 24.1.1 | 3 / 0 | |
| 24.1.0 | 3 / 0 | |
| 23.3.0 | 22 / 0 | |
| 23.2.2 | 22 / 0 | |
| 23.2.1 | 22 / 0 | |
| 23.2.0 | 22 / 0 | |
| 23.1.1 | 22 / 0 | |
| 23.1.0 | 22 / 0 | |
| 23.0.4 | 22 / 0 | |
| 23.0.3 | 22 / 0 | |
| 23.0.2 | 22 / 0 | |
| 23.0.1 | 22 / 0 | |
| 23.0.0 | 22 / 0 | |
| 22.1.9 | 21 / 0 | |
| 22.1.8 | 21 / 0 | |
| 22.1.7 | 21 / 0 | |
| 22.1.6 | 21 / 0 | |
| 22.1.5 | 21 / 0 | |
| 22.1.4 | 21 / 0 |
v32.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.