markdown-utils 0.1.3
Create markdown snippets.
markdown-utils@0.1.3 was published on 2014-11-19. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All markdown-utils versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | Not declared |
| Published | 2014-11-19T13:32:29.128Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 29 |
| Repository forks | 7 |
Install markdown-utils 0.1.3
npm install markdown-utils@0.1.3 pnpm add markdown-utils@0.1.3 yarn add markdown-utils@0.1.3
Runtime dependencies
- export-files ^0.1.4
- repeat-string ^0.2.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- export-files@0.1.4 — direct
- repeat-string@0.2.2 — direct
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/27 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/markdown-utils/0.1.3 — retrieved 2026-10-29T22:15:55.588Z
- https://api.deps.dev/v3/systems/npm/packages/markdown-utils/versions/0.1.3 — retrieved 2026-10-29T22:15:56.104Z
- https://api.deps.dev/v3/systems/npm/packages/markdown-utils/versions/0.1.3:dependencies — retrieved 2026-10-29T22:15:56.140Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fmarkdown-utils — retrieved 2026-10-29T22:15:56.761Z