@codingame/monaco-vscode-all-default-extensions
Meta package including default VSCode extensions designed to be used with @codingame/monaco-vscode-api
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA provenance attestation; stable for this package going forward. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance via GitHub Actions. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-theme-2026-default-extension | AI (dependencies): Follows identical naming/versioning pattern as all other @codingame/monaco-vscode-theme-*-default-extension deps; consistent with package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Established CodinGame package family; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@codingame/monaco-vscode-microsoft-authentication-default-extension | AI (dependencies): Same publisher/namespace/version as the parent package; sibling dep within the CodinGame monaco-vscode-api monorepo. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 33.0.9 | 79 / 0 | |
| 33.0.8 | 79 / 0 | |
| 33.0.7 | 79 / 0 | |
| 33.0.6 | 79 / 0 | |
| 33.0.5 | 79 / 0 | |
| 33.0.4 | 79 / 0 | |
| 33.0.3 | 79 / 0 | |
| 32.0.2 | 79 / 0 | |
| 32.0.1 | 79 / 0 | |
| 32.0.0 | 79 / 0 | |
| 31.0.1 | 79 / 0 | |
| 31.0.0 | 79 / 0 | |
| 30.0.1 | 79 / 0 | |
| 30.0.0 | 79 / 0 | |
| 29.1.1 | 79 / 0 | |
| 29.1.0 | 79 / 0 | |
| 29.0.0 | 79 / 0 | |
| 28.4.1 | 80 / 0 | |
| 28.3.0 | 80 / 0 | |
| 28.1.2 | 80 / 0 | |
| 28.1.1 | 80 / 0 | |
| 28.0.0 | 80 / 0 | |
| 27.0.0 | 80 / 0 | |
| 26.2.2 | 80 / 0 | |
| 26.2.0 | 80 / 0 | |
| 26.1.2 | 80 / 0 | |
| 26.1.1 | 80 / 0 | |
| 26.0.0 | 80 / 0 | |
| 25.1.2 | 79 / 0 | |
| 25.1.1 | 79 / 0 | |
| 25.1.0 | 79 / 0 | |
| 25.0.1 | 79 / 0 | |
| 25.0.0 | 79 / 0 | |
| 24.3.0 | 79 / 0 | |
| 24.2.0 | 79 / 0 | |
| 24.1.1 | 79 / 0 | |
| 24.1.0 | 79 / 0 | |
| 23.2.2 | 80 / 0 | |
| 23.2.1 | 80 / 0 | |
| 23.2.0 | 80 / 0 | |
| 23.1.1 | 80 / 0 | |
| 23.1.0 | 80 / 0 | |
| 23.0.4 | 80 / 0 | |
| 23.0.3 | 80 / 0 | |
| 23.0.2 | 80 / 0 | |
| 23.0.1 | 80 / 0 | |
| 23.0.0 | 80 / 0 | |
| 22.1.9 | 79 / 0 | |
| 22.1.8 | 79 / 0 | |
| 22.1.7 | 79 / 0 | |
| 22.1.6 | 79 / 0 |
v33.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v32.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.