@ws-ui/code-editor
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Component library with peer deps; phantom-dep heuristic fires on config-referenced deps, stable FP. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dependency pattern for React component library; stable FP. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:react-icons | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:re-resizable | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:react-popper | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:simplebar-react | AI (phantom-deps): Stable FP for this component library's dependency structure. | ai | |
| phantom-deps | phantom-dep:@codingame/monaco-vscode-model-service-override | AI (phantom-deps): Monaco ecosystem dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@codingame/monaco-vscode-monarch-service-override | AI (phantom-deps): Monaco ecosystem dep; stable FP for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.13.3 | 34 / 17 | |
| 1.13.2 | 34 / 17 | |
| 1.13.1 | 34 / 17 | |
| 1.13.0 | 34 / 17 | |
| 1.12.4 | 34 / 17 | |
| 1.12.3 | 34 / 17 | |
| 1.12.2 | 34 / 17 | |
| 1.12.1 | 34 / 17 |
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
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 (idrissi) than the most recent previously approved version (axel-dev) on 2026-05-22, but idrissi 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.
v1.13.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 (idrissi) than the most recent previously approved version (axel-dev) on 2026-05-20, but idrissi 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.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.