pretty-remarkable MIT 24 versions

pretty-remarkable

npm Repository Homepage

Plugin for prettifying markdown with Remarkable using custom renderer rules.

24

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

jonschlinkert

Keywords

beautifyformatmarkdownmarkedmdpluginprettifyprettyremarkable

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Package is 4015 days old, predating Sigstore provenance. Established publisher with strong track record; lack of provenance is expected for this package's age.	ai	2026/04/24
phantom-deps	phantom-dep:list-item	AI (phantom-deps): Plugin package; list-item is a legitimate runtime dependency used indirectly through the plugin system.	ai	2026/04/24
phantom-deps	phantom-dep:remarkable	AI (phantom-deps): Plugin package; remarkable is the core dependency this package wraps and extends.	ai	2026/04/24
phantom-deps	phantom-dep:repeat-string	AI (phantom-deps): Plugin package; repeat-string is a legitimate runtime dependency used indirectly.	ai	2026/04/24
phantom-deps	phantom-dep:extend-shallow	AI (phantom-deps): Plugin package; extend-shallow is a legitimate runtime dependency used indirectly.	ai	2026/04/24

Versions (showing 24 of 24)

Version	Deps	Published
1.0.0	1 / 3	2018-07-05
0.4.1	5 / 4	2017-04-04
0.4.0	5 / 4	2016-10-21
0.3.10	4 / 3	2016-09-27
0.3.9	4 / 3	2016-07-07
0.3.8	4 / 3	2016-07-02
0.3.7	4 / 3	2016-06-30
0.3.6	4 / 3	2016-05-03
0.3.4	4 / 3	2016-04-27
0.3.2	4 / 3	2016-04-26
0.3.1	4 / 3	2016-04-23
0.3.0	4 / 3	2016-04-23
0.2.2	4 / 3	2016-04-17
0.2.1	4 / 3	2016-03-23
0.2.0	4 / 2	2015-12-16
0.1.8	4 / 3	2015-06-13
0.1.7	4 / 3	2015-06-09
0.1.6	4 / 3	2015-06-09
0.1.5	4 / 3	2015-06-09
0.1.4	3 / 3	2015-04-27
0.1.3	4 / 3	2015-04-27
0.1.2	2 / 3	2015-04-27
0.1.1	2 / 3	2015-04-27
0.1.0	4 / 2	2015-04-27

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.

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

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.

v0.1.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.