@codingame/monaco-vscode-preferences-service-override
VSCode public API plugged on the monaco editor - preferences 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-02fe61a6-05e4-5021-8c27-16e910b9182c-common | AI (dependencies): Internal monorepo sub-package from same trusted publisher; UUID naming is a known pattern for this package family. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-2808e692-5fb9-54bf-bc21-1d3bff81e651-common | AI (dependencies): Internal monorepo sub-package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-3692fc2f-920d-56ed-accd-d988be683cc3-common | AI (dependencies): Internal monorepo sub-package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-7b19b93e-7a49-5c48-81f5-091a64f468d2-common | AI (dependencies): Internal monorepo sub-package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-dd5b2d07-86ca-557c-8510-224a400e258d-common | AI (dependencies): Internal monorepo sub-package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-a3eaa464-944c-5b8f-8886-213068ba4897-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-c3b3387c-7bce-5b8f-9e14-bebeb636f1c8-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-37b3b402-09f5-5f69-89ef-ce30559f63cc-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-dc3fa21d-a483-5b99-a7ab-173235644a34-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-e72c94ca-257a-5b75-8b68-5a5fa3c18255-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-ce7c734f-7712-563c-9335-d7acb43306af-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-422642f2-7e3a-5c1c-9e1e-1d3ef1817346-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-7869cfe8-f42c-5721-9f2b-7d04a6a41f16-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-8bcd87e5-7461-57cf-b4e4-a7b00d2b33df-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-9efc1f50-c7de-55d6-8b28-bcc88bd49b5a-common | AI (dependencies): Internal monorepo sub-package; UUID naming is CodinGame's established code-splitting pattern. | ai |
Versions (showing 52 of 52)
| 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 | 19 / 0 | |
| 23.2.2 | 19 / 0 | |
| 23.2.1 | 19 / 0 | |
| 23.2.0 | 19 / 0 | |
| 23.1.1 | 19 / 0 | |
| 23.1.0 | 19 / 0 | |
| 23.0.4 | 19 / 0 | |
| 23.0.3 | 19 / 0 | |
| 23.0.2 | 19 / 0 | |
| 23.0.1 | 19 / 0 | |
| 23.0.0 | 19 / 0 | |
| 22.1.9 | 18 / 0 | |
| 22.1.8 | 18 / 0 | |
| 22.1.7 | 18 / 0 | |
| 22.1.6 | 18 / 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. 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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. 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.
v22.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.