remarkable
Markdown parser, done right. 100% Commonmark support, extensions, syntax plugins, high speed - all in one.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition to trysound, a well-established publisher (1507 approved versions, 11yr history). Original maintainers retained in package.json. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): spicyj removed likely reflects sophiebits username change (same person: Sophie Alpert). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers (matthewmueller, sophiebits, trysound) are known community members; legitimate transition. | ai | |
| provenance | missing-githead | AI (provenance): Expected when publish environment changes during maintainer transition; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): remarkable predates Sigstore provenance; absence is expected and stable for this package. | ai | |
| source-diff | net-exec-file:dist/cjs/index.browser.js | AI (source-diff): Bundled markdown parser code; innerHTML for entity decoding is not a network call. False positive on remarkable's standard dist output. | ai | |
| source-diff | net-exec-file:dist/esm/index.js | AI (source-diff): ESM bundle of remarkable with entity table; no actual network or malicious exec. Standard dist output. | ai | |
| source-diff | net-exec-file:dist/esm/index.browser.js | AI (source-diff): ESM browser bundle of remarkable; innerHTML entity decoding misclassified as network call. Standard dist output. | ai | |
| source-diff | net-exec-file:dist/cjs/index.js | AI (source-diff): Bundled markdown parser with HTML entity table; no actual network or malicious exec patterns. Standard dist output. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 2 / 16 | |
| 2.0.0 | 2 / 16 | |
| 1.7.4 | 2 / 9 | |
| 1.7.3 | 2 / 9 | |
| 1.7.2 | 2 / 8 | |
| 0.1.0 | 0 / 2 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trysound.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trysound.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trysound.
v1.7.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trysound.
This version was published by a different npm account than previous versions on 2019-07-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.