← Home

@codingame/monaco-vscode-e28ac690-06d5-5ee9-92d1-02df70296354-common

npm Repository Homepage
16
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
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects versioned release cadence for this monaco-vscode-api sub-package family, not account takeover. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are same-version sibling packages from the same CodinGame publisher, consistent with internal refactoring. ai
dependencies unvetted-dep:@codingame/monaco-vscode-afb6e5ca-fe46-5d5a-aa9c-f722ebefae39-common AI (dependencies): Sibling package from same publisher/ecosystem; naming convention matches all other deps in this family. ai
dependencies unvetted-dep:@codingame/monaco-vscode-ac93482b-2178-52df-a200-ba0d1a4963fb-common AI (dependencies): Same-org monorepo sibling package; released in lockstep at identical version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-bd0792ac-6043-5ec3-a41a-54ccb922a1f4-common AI (dependencies): Same-org monorepo sibling package; released in lockstep at identical version. ai
dependencies unvetted-dep:@codingame/monaco-vscode-be143a32-d60a-5489-a1d2-c83ea7eff6bf-common AI (dependencies): Same-org monorepo sibling package; released in lockstep at identical version. ai

Versions (showing 16 of 16)

Version Deps Published
23.3.0 13 / 0
23.2.2 13 / 0
23.2.1 13 / 0
23.2.0 13 / 0
23.1.1 13 / 0
23.1.0 13 / 0
23.0.4 13 / 0
23.0.3 13 / 0
23.0.2 13 / 0
23.0.1 13 / 0
23.0.0 13 / 0
22.1.9 25 / 0
22.1.8 25 / 0
22.1.7 25 / 0
22.1.6 25 / 0
22.1.5 25 / 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
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

v22.1.8

1 finding
LOW No provenance attestation provenance

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