← Home

markdown-utils

npm Repository Homepage

Tiny helpers for creating consistenly-formatted markdown snippets.

16
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

adjohnson916doowbjonschlinkert

Keywords

blogcommonmarkmarkdownmarkdown-itmdpostremarkremarkabletextutilswrite

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change adjohnson916 → jonschlinkert reflects a legitimate 2016 transfer to the package's listed author who owns the GitHub repo. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): doowb is a known collaborator in jonschlinkert's ecosystem; addition is consistent with legitimate maintainer management. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads only local sibling .js files bundled within the package itself via filter-files; no external or user-controlled input influences the path. Stable false positive for this package. ai

Versions (showing 16 of 16)

Version Deps Published
1.0.0 2 / 2
0.7.3 4 / 3
0.7.2 4 / 2
0.7.1 4 / 3
0.7.0 4 / 2
0.6.1 3 / 2
0.6.0 3 / 2
0.5.0 4 / 2
0.4.0 5 / 2
0.3.0 4 / 4
0.2.1 4 / 4
0.2.0 2 / 4
0.1.3 2 / 4
0.1.2 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.7.3

2 findings
HIGH Publisher changed: adjohnson916 → jonschlinkert (on 2016-04-23) provenance

This version was published by a different npm account than previous versions on 2016-04-23. 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.7.2

2 findings
HIGH Publisher changed: adjohnson916 → jonschlinkert (on 2016-04-23) provenance

This version was published by a different npm account than previous versions on 2016-04-23. 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.7.1

2 findings
HIGH Publisher changed: jonschlinkert → adjohnson916 (on 2015-08-09) provenance

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

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

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