← Home

remarked

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

codecompilecompilerdocsdocumentationfencesflavoredgfmgithubhtmljsjavascriptnode.jslexlexermarkdownmarkedmarkupparseparserprocessingprocessorrenderrenderertabletablestexttokenizer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process usage is limited to spawning 'man' for CLI help display — a standard, benign pattern for CLI tools with man page documentation. Not a security risk for this package. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.4 2 / 9
0.1.3 4 / 10
0.1.2 4 / 10

v0.1.4

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

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

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.