@codingame/monaco-vscode-markdown-language-features-default-extension
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 publisher is backed by SLSA provenance attestation; consistent with CI/CD automation adoption. | ai | |
| bogus-package | bogus-package | AI (bogus-package): VSCode extension wrapper; sparse README and no keywords are expected for this package type. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 34.1.3 | 1 / 0 | |
| 34.1.1 | 1 / 0 | |
| 34.1.0 | 1 / 0 | |
| 34.0.3 | 1 / 0 | |
| 34.0.2 | 1 / 0 | |
| 34.0.1 | 1 / 0 | |
| 34.0.0 | 1 / 0 | |
| 33.0.9 | 1 / 0 | |
| 33.0.7 | 1 / 0 | |
| 32.0.2 | 1 / 0 | |
| 32.0.1 | 1 / 0 | |
| 32.0.0 | 1 / 0 | |
| 31.0.1 | 1 / 0 | |
| 31.0.0 | 1 / 0 | |
| 30.0.1 | 1 / 0 | |
| 30.0.0 | 1 / 0 | |
| 29.1.1 | 1 / 0 | |
| 29.1.0 | 1 / 0 | |
| 29.0.0 | 1 / 0 | |
| 28.4.1 | 1 / 0 | |
| 28.4.0 | 1 / 0 | |
| 28.3.1 | 1 / 0 | |
| 28.3.0 | 1 / 0 | |
| 28.2.0 | 1 / 0 | |
| 28.1.2 | 1 / 0 | |
| 28.1.1 | 1 / 0 | |
| 28.0.1 | 1 / 0 | |
| 28.0.0 | 1 / 0 | |
| 27.0.0 | 1 / 0 | |
| 26.2.2 | 1 / 0 | |
| 26.2.1 | 1 / 0 | |
| 26.2.0 | 1 / 0 | |
| 26.1.2 | 1 / 0 | |
| 26.1.1 | 1 / 0 | |
| 26.1.0 | 1 / 0 | |
| 26.0.1 | 1 / 0 | |
| 26.0.0 | 1 / 0 | |
| 25.1.2 | 1 / 0 | |
| 25.1.1 | 1 / 0 | |
| 25.1.0 | 1 / 0 | |
| 25.0.1 | 1 / 0 | |
| 25.0.0 | 1 / 0 | |
| 24.3.0 | 1 / 0 | |
| 24.2.0 | 1 / 0 | |
| 24.1.1 | 1 / 0 | |
| 24.1.0 | 1 / 0 | |
| 23.3.0 | 1 / 0 | |
| 23.2.2 | 1 / 0 | |
| 23.2.1 | 1 / 0 | |
| 23.2.0 | 1 / 0 | |
| 23.1.1 | 1 / 0 |
v34.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v28.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.3.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.2.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.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.1
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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samuel.olivier) than the most recent previously approved version (codingame_team) on 2025-12-18, but samuel.olivier is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v24.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samuel.olivier) than the most recent previously approved version (codingame_team) on 2025-12-18, but samuel.olivier is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v23.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.