← Home

@codingame/monaco-vscode-a793b3ee-7ba9-5176-a019-30ec806fdd95-common

15
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

nonofrsamuel.oliviernantoniazzimaximecgcodingame_team

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size increase aligns with new chat UI modules (chatWidget, chatInputPart, etc.) — expected for this package's pattern. ai
source-diff large-new-source-files AI (source-diff): CodinGame monorepo regularly ships large VSCode source bundles; size growth matches chat feature addition. ai
dependencies unvetted-dep:@codingame/monaco-vscode-5b8cf422-a92f-53bb-aa8a-d9c56494b1e6-common AI (dependencies): Sibling package from same CodinGame monorepo, released in lockstep at same version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-7aa7b0aa-41af-57b3-860a-86d2f987a6c8-common AI (dependencies): Sibling package from same CodinGame monorepo, released in lockstep at same version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-e7e3c399-ecb3-58fd-82d6-1d2f4e38813e-common AI (dependencies): Sibling package from same CodinGame monorepo, released in lockstep at same version. ai
provenance no-provenance AI (provenance): CodinGame does not use Sigstore provenance; consistent across all their packages. ai
dependencies unvetted-dep:@codingame/monaco-vscode-8d4ef243-d8c1-540d-9f11-38df46f54c9f-common AI (dependencies): Sibling package from same CodinGame monorepo, released in lockstep at same version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-2808e692-5fb9-54bf-bc21-1d3bff81e651-common AI (dependencies): Sibling package from same CodinGame monorepo, released in lockstep at same version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-ac93482b-2178-52df-a200-ba0d1a4963fb-common AI (dependencies): Sibling package from same CodinGame monorepo; unvetted only because it hasn't been reviewed yet, not a risk signal. ai
dependencies unvetted-dep:@codingame/monaco-vscode-e28ac690-06d5-5ee9-92d1-02df70296354-common AI (dependencies): Sibling package from same CodinGame monorepo; unvetted only because it hasn't been reviewed yet, not a risk signal. ai

Versions (showing 15 of 15)

Version Deps Published
23.3.0 24 / 0
23.2.2 24 / 0
23.2.1 24 / 0
23.2.0 24 / 0
23.1.1 24 / 0
23.1.0 26 / 0
23.0.4 26 / 0
23.0.3 26 / 0
23.0.2 26 / 0
23.0.1 26 / 0
23.0.0 26 / 0
22.1.8 8 / 0
22.1.7 8 / 0
22.1.6 8 / 0
22.1.5 8 / 0

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
INFO No provenance attestation provenance

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

v23.2.1

1 finding
INFO No provenance attestation provenance

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

v23.2.0

1 finding
INFO No provenance attestation provenance

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

v23.1.1

1 finding
INFO No provenance attestation provenance

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

v23.1.0

1 finding
INFO No provenance attestation provenance

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

v23.0.4

1 finding
INFO No provenance attestation provenance

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

v23.0.3

1 finding
INFO No provenance attestation provenance

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

v23.0.2

1 finding
INFO No provenance attestation provenance

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

v23.0.1

1 finding
INFO No provenance attestation provenance

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

v23.0.0

1 finding
INFO No provenance attestation provenance

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

v22.1.8

1 finding
INFO No provenance attestation provenance

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

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
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

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