remove-markdown MIT 20 versions

remove-markdown

npm Repository Homepage

Remove Markdown formatting from text

20

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

stiangzuchka

Keywords

markdown

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from stiang to zuchka is consistent with a legitimate transfer; repo URL updated to match new owner, no malicious code changes, publisher has strong track record.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer zuchka has 19 approved packages and 629-day history; transfer appears legitimate given matching repo URL and no code changes.	ai	2026/04/23

Versions (showing 20 of 20)

Version	Deps	Published
0.6.4	0 / 3	2026-05-09
0.6.3	0 / 3	2026-01-15
0.6.2	0 / 3	2025-05-02
0.6.1	0 / 3	2025-05-02
0.6.0	0 / 3	2024-12-16
0.5.5	0 / 3	2024-09-01
0.5.4	0 / 3	2024-09-01
0.5.3	0 / 3	2024-08-29
0.5.2	0 / 3	2024-08-02
0.5.0	0 / 3	2022-04-27
0.3.0	0 / 3	2018-05-27
0.2.2	0 / 3	2017-08-12
0.2.1	0 / 3	2017-08-02
0.2.0	0 / 3	2017-06-21
0.1.0	0 / 2	2016-01-18
0.0.6	0 / 2	2015-07-15
0.0.5	0 / 2	2015-05-20
0.0.4	0 / 2	2015-05-20
0.0.2	0 / 2	2015-02-15
0.0.1	0 / 2	2015-02-15

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.5

2 findings

HIGH Publisher changed: stiang → zuchka (on 2024-09-01) provenance

This version was published by a different npm account than previous versions on 2024-09-01. 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.

v0.5.4

2 findings

HIGH Publisher changed: stiang → zuchka (on 2024-09-01) provenance

This version was published by a different npm account than previous versions on 2024-09-01. 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.

v0.5.3

2 findings

HIGH Publisher changed: stiang → zuchka (on 2024-08-29) provenance

This version was published by a different npm account than previous versions on 2024-08-29. 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.

v0.5.2

2 findings

HIGH Publisher changed: stiang → zuchka (on 2024-08-02) provenance

This version was published by a different npm account than previous versions on 2024-08-02. 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.

v0.5.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.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.0

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

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