marked-terminal

A custom render for marked to output to the Terminal

marked-terminal@7.3.1 was published on 2026-10-28. Its manifest declares 7 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=16.0.0.

All marked-terminal versions · Permanent reference to 7.3.1

Package specifications

Version7.3.1
License declarationMIT
Published2026-10-28T19:26:04.821Z
Node.js requirement>=16.0.0
Type declarationsNot declared
Runtime dependency count7
Peer requirement count1
Optional dependency count0
Minified size1304.47 KiB
Minified + gzip379.57 KiB
Unpacked distribution size1915.68 KiB
Published file count5
Package typemodule
ES module entryNot declared
Default entry./index.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars501
Repository forks71

Install marked-terminal 7.3.1

npm install marked-terminal@7.3.1
pnpm add marked-terminal@7.3.1
yarn add marked-terminal@7.3.1

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review4/10 — Found 4/10 approved changesets -- score normalized to 4
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness