@panneau/ckeditor
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
Keywords
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): Publisher is a known maintainer on prior approved versions; dormancy explained by version gap, not account takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description in a monorepo package; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-react | AI (phantom-deps): Peer/runtime dep used via config, not direct import; stable pattern. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-dev-utils | AI (phantom-deps): Build-tool dep referenced in webpack config, not imported at runtime; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@folklore/fetch | AI (phantom-deps): Sibling org package referenced in config; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-theme-lark | AI (phantom-deps): CKEditor theme dep referenced in build config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@ckeditor/ckeditor5-dev-translations | AI (phantom-deps): Build-tool dep referenced in webpack config; stable pattern for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.0.41 | 14 / 2 | |
| 4.0.37 | 14 / 2 | |
| 4.0.21 | 14 / 2 | |
| 4.0.19 | 14 / 2 | |
| 4.0.14 | 14 / 2 | |
| 4.0.11 | 14 / 2 | |
| 4.0.0 | 14 / 2 | |
| 3.0.319 | 14 / 2 | |
| 3.0.317 | 14 / 2 |
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2026-02-25, but dmongeau 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.
v4.0.11
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2026-02-24, but dmongeau 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.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.319
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2025-12-17, but dmongeau 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.
v3.0.317
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2025-12-16, but dmongeau 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.