← Home

react-remarkable

npm Repository Homepage

A React component for rendering Markdown with remarkable

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mxstbracdlite

Keywords

reactremarkablemarkdowncommonmark

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change acdlite→mxstbr occurred in 2017; mxstbr is a well-known React ecosystem maintainer with a strong track record. Legitimate handoff, stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): mxstbr is a highly reputable npm publisher (5827 approved packages, 0 rejected). Maintainer addition is a known legitimate transition for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.3 1 / 1
1.1.2 1 / 1
1.1.1 1 / 1
1.1.0 2 / 1
1.0.0 2 / 1

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

2 findings
HIGH Publisher changed: acdlite → mxstbr (on 2017-09-26) provenance

This version was published by a different npm account than previous versions on 2017-09-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.