@codingame/monaco-vscode-71c8dbff-4c98-552f-aef0-e72b00fdcfc0-common MIT 14 versions

@codingame/monaco-vscode-71c8dbff-4c98-552f-aef0-e72b00fdcfc0-common

npm Repository Homepage

VSCode public API plugged on the monaco editor - common package (bulk-edit, chat, debug, edit-sessions, explorer, extension-gallery, extensions, interactive, markers, mcp, notebook, outline, output, remote-agent, scm, search, task, terminal, testing, time

14

Versions

MIT

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nonofrsamuel.oliviernantoniazzimaximecgcodingame_team

Versions (showing 14 of 14)

Version	Deps	Published
21.6.0	3 / 0	2025-10-09
21.5.1	3 / 0	2025-10-08
21.5.0	3 / 0	2025-10-08
21.4.0	3 / 0	2025-10-06
21.3.4	3 / 0	2025-10-01
21.3.3	3 / 0	2025-10-01
21.3.2	3 / 0	2025-09-30
21.3.1	3 / 0	2025-09-29
21.3.0	3 / 0	2025-09-26
21.2.1	3 / 0	2025-09-23
21.2.0	3 / 0	2025-09-23
21.1.0	3 / 0	2025-09-18
21.0.1	3 / 0	2025-09-15
21.0.0	3 / 0	2025-09-12

v21.6.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.

v21.5.1

1 finding

LOW No provenance attestation provenance

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

v21.5.0

1 finding

LOW No provenance attestation provenance

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

v21.4.0

1 finding

LOW No provenance attestation provenance

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

v21.3.4

1 finding

LOW No provenance attestation provenance

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

v21.3.3

1 finding

LOW No provenance attestation provenance

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

v21.3.2

1 finding

LOW No provenance attestation provenance

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

v21.3.1

1 finding

LOW No provenance attestation provenance

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

v21.3.0

1 finding

LOW No provenance attestation provenance

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

v21.2.1

1 finding

LOW No provenance attestation provenance

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

v21.2.0

1 finding

LOW No provenance attestation provenance

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

v21.1.0

1 finding

LOW No provenance attestation provenance

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

v21.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.

v21.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.