@ckeditor/ckeditor5-markdown-gfm
GitHub Flavored Markdown data processor for CKEditor 5.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/markdown-gfm.js | AI (source-diff): Standard CKEditor5 DLL webpack bundle in build/ directory; minified output, not obfuscated. Consistent across all ckeditor5-* packages. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from adding build/ directory with DLL bundle — standard CKEditor5 distribution pattern. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is common across npm; not a disqualifier for established packages with strong ecosystem trust. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Standard CKEditor practice; actual license is in the repository. | ai | |
| dependencies | unvetted-dep:remark-breaks | AI (dependencies): Established remark plugin with wide adoption; no security concerns. | ai | |
| dependencies | unvetted-dep:rehype-dom-parse | AI (dependencies): Established rehype ecosystem package; no security concerns. | ai | |
| dependencies | unvetted-dep:hast-util-from-dom | AI (dependencies): Established hast utility package; no security concerns. | ai | |
| dependencies | unvetted-dep:hast-util-to-mdast | AI (dependencies): Established hast utility package; no security concerns. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-core | AI (dependencies): Official CKEditor 5 sibling package published by the same ckeditor org; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@types/hast | AI (dependencies): TypeScript type declarations package from DefinitelyTyped; no runtime security risk. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): Type-only package used at compile time; not being directly imported at runtime is expected behavior. | ai | |
| phantom-deps | phantom-dep:hast-util-to-mdast | AI (phantom-deps): Referenced in config files rather than direct imports; legitimate usage pattern for this package. | ai | |
| dependencies | unvetted-dep:rehype-dom-stringify | AI (dependencies): Established rehype ecosystem package; no security concerns. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-engine | AI (dependencies): Official CKEditor 5 sibling package published by the same ckeditor org; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@ckeditor/ckeditor5-clipboard | AI (dependencies): Official CKEditor 5 sibling package published by the same ckeditor org; unvetted status is a pipeline gap, not a security concern. | ai | |
| dependencies | unvetted-dep:rehype-remark | AI (dependencies): Established unified ecosystem package with wide adoption; no security concerns. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 48.2.0 | 18 / 0 | |
| 48.1.1 | 18 / 0 | |
| 48.1.0 | 18 / 0 | |
| 48.0.1 | 18 / 0 | |
| 48.0.0 | 18 / 0 | |
| 47.7.2 | 19 / 0 | |
| 47.7.1 | 19 / 0 | |
| 47.7.0 | 19 / 0 | |
| 47.6.2 | 19 / 0 | |
| 47.6.1 | 19 / 0 | |
| 47.6.0 | 19 / 0 | |
| 47.5.0 | 19 / 0 | |
| 47.4.0 | 19 / 0 | |
| 47.3.0 | 19 / 0 | |
| 47.2.0 | 19 / 0 |
v48.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v48.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v47.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.