← Home

@codingame/monaco-vscode-4ee27008-17b4-593f-9c09-19e8e3077f51-common

npm Repository Homepage

VSCode public API plugged on the monaco editor - common package (bulk-edit, chat, editor, explorer, extensions, interactive, mcp, model, notebook, output, performance, search, terminal, view-common, views, workbench)

9
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@codingame/monaco-vscode-ed7f2efb-131f-5ae8-b8fe-f20867e14c58-common AI (dependencies): Same-org generated sub-package, part of normal codegen dependency churn. ai
publish-pattern new-deps-added AI (publish-pattern): Expected churn in auto-generated monaco-vscode-api sub-packages, not a novel external dep. ai

Versions (showing 9 of 9)

Version Deps Published
18.4.0 2 / 0
18.2.2 2 / 0
18.2.0 2 / 0
18.1.3 2 / 0
18.1.2 2 / 0
18.1.1 2 / 0
18.1.0 2 / 0
18.0.1 2 / 0
18.0.0 2 / 0

v18.4.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.

v18.2.2

1 finding
LOW No provenance attestation provenance

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

v18.2.0

1 finding
LOW No provenance attestation provenance

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

v18.1.3

1 finding
LOW No provenance attestation provenance

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

v18.1.2

1 finding
LOW No provenance attestation provenance

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

v18.1.1

1 finding
LOW No provenance attestation provenance

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

v18.1.0

1 finding
LOW No provenance attestation provenance

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

v18.0.1

1 finding
LOW No provenance attestation provenance

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

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