@codingame/monaco-vscode-88aa9a78-75f5-5aaa-89e9-bbdd580b3b5c-common
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): CodinGame publishes many sub-packages; gaps in individual sub-package cadence are expected and not indicative of takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org, same-version internal packages; consistent with routine internal refactoring. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 23.3.0 | 7 / 0 | |
| 23.2.2 | 7 / 0 | |
| 23.2.1 | 7 / 0 | |
| 23.2.0 | 7 / 0 | |
| 23.1.1 | 7 / 0 | |
| 23.1.0 | 7 / 0 | |
| 23.0.4 | 7 / 0 | |
| 23.0.3 | 7 / 0 | |
| 23.0.2 | 7 / 0 | |
| 23.0.1 | 7 / 0 | |
| 23.0.0 | 7 / 0 | |
| 22.1.9 | 7 / 0 | |
| 22.1.8 | 7 / 0 | |
| 22.1.7 | 7 / 0 | |
| 22.1.6 | 7 / 0 | |
| 22.1.5 | 7 / 0 |
v23.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.