@codingame/monaco-vscode-scm-service-override
VSCode public API plugged on the monaco editor - scm 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-ef4149eb-cc74-500f-a75b-c54539f01afa-common | AI (dependencies): Internal CodinGame sub-package, consistent naming pattern across all versions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-05c09f77-cd1d-5960-b387-e7023df3160b-common | AI (dependencies): Internal CodinGame sub-package following established UUID bundle pattern; same org and version. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-2339d6ac-d6bb-53cd-95ee-81911735d1c7-common | AI (dependencies): Internal CodinGame sub-package following established UUID bundle pattern; same org and version. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-2c64d2c2-fdf7-5675-a2fe-f6f65fbdedbf-common | AI (dependencies): Internal CodinGame sub-package following established UUID bundle pattern; same org and version. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-09e9b2e8-42a8-5a68-864f-bfcdad0ca1df-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-ff9fa663-eae3-5274-8573-c2b918871e4b-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-dbfe5f85-b426-55ed-a79b-5f811b395762-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-27663a0b-1249-58ba-9085-e52d706b50bc-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-bb83fe45-f4c7-5673-b9f1-5c409a63f19c-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-c2deffc4-ad68-5e63-8f95-9b89e0fc6898-common | AI (dependencies): Internal CodinGame monorepo sub-package; UUID naming is a build artifact pattern, not a supply-chain risk. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 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 | 12 / 0 | |
| 23.0.4 | 12 / 0 | |
| 23.0.3 | 12 / 0 | |
| 23.0.2 | 12 / 0 | |
| 23.0.1 | 12 / 0 | |
| 23.0.0 | 12 / 0 | |
| 22.1.9 | 14 / 0 | |
| 22.1.8 | 14 / 0 | |
| 22.1.7 | 14 / 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. 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. 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. 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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.