@codingame/monaco-vscode-scm-service-override MIT 54 versions

@codingame/monaco-vscode-scm-service-override

npm Repository Homepage

VSCode public API plugged on the monaco editor - scm service-override

54

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nonofrsamuel.oliviernantoniazzimaximecgcodingame_team

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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06
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	2026/05/06

Versions (showing 54 of 54)

Version	Deps	Published
32.0.2	1 / 0	2026-05-15
32.0.1	1 / 0	2026-05-15
32.0.0	1 / 0	2026-05-13
31.0.1	1 / 0	2026-05-07
31.0.0	1 / 0	2026-04-28
30.0.1	1 / 0	2026-04-13
30.0.0	1 / 0	2026-04-01
29.1.1	1 / 0	2026-03-31
29.1.0	1 / 0	2026-03-31
29.0.0	1 / 0	2026-03-30
28.4.1	1 / 0	2026-03-23
28.4.0	1 / 0	2026-03-23
28.3.1	1 / 0	2026-03-20
28.3.0	1 / 0	2026-03-19
28.2.0	1 / 0	2026-03-18
28.1.2	1 / 0	2026-03-18
28.1.1	1 / 0	2026-03-17
28.0.1	1 / 0	2026-03-10
28.0.0	1 / 0	2026-03-09
27.0.0	1 / 0	2026-03-05
26.2.2	1 / 0	2026-03-05
26.2.1	1 / 0	2026-02-23
26.2.0	1 / 0	2026-02-19
26.1.2	1 / 0	2026-02-13
26.1.1	1 / 0	2026-02-12
26.1.0	1 / 0	2026-02-11
26.0.1	1 / 0	2026-02-10
26.0.0	1 / 0	2026-02-09
25.1.2	1 / 0	2026-02-03
25.1.1	1 / 0	2026-02-02
25.1.0	1 / 0	2026-01-29
25.0.1	1 / 0	2026-01-21
25.0.0	1 / 0	2026-01-12
24.3.0	1 / 0	2026-01-07
24.2.0	1 / 0	2025-12-19
24.1.1	1 / 0	2025-12-18
24.1.0	1 / 0	2025-12-18
23.3.0	13 / 0	2025-12-09
23.2.2	13 / 0	2025-11-26
23.2.1	13 / 0	2025-11-25
23.2.0	13 / 0	2025-11-25
23.1.1	13 / 0	2025-11-24
23.1.0	12 / 0	2025-11-21
23.0.4	12 / 0	2025-11-20
23.0.3	12 / 0	2025-11-17
23.0.2	12 / 0	2025-11-17
23.0.1	12 / 0	2025-11-17
23.0.0	12 / 0	2025-11-14
22.1.9	14 / 0	2025-11-12
22.1.8	14 / 0	2025-11-10
22.1.7	14 / 0	2025-11-10
22.1.6	14 / 0	2025-11-10
22.1.5	14 / 0	2025-11-10
22.1.4	14 / 0	2025-11-04

v32.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v32.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v31.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v31.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.1.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v28.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.1.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v23.2.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.0.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.1.9

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v22.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v22.1.6

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.