monaco-editor-webpack-plugin
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Microsoft org handoff to vscode-bot/team maintainers, consistent with repo ownership. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Prior individual maintainer removed as part of same org transfer. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change to official vscode-bot, not a takeover pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by low-churn maintenance package, not suspicious given trusted publisher. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads monaco-editor metadata.js via resolved path; standard webpack plugin pattern, not a security risk. | ai |
v7.1.0
2 findingsThis version was published by a different npm account (vscode-bot) than the most recent previously approved version (alexandrudima) on 2023-07-10. It has since remained available on npm for 1105 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.