extract-gfm
Utilities for extracting and replacing GitHub Flavored Markdown code blocks. For example, you could easily find code blocks for a specific language and run the code through a linter.
extract-gfm@0.1.0 was published on 2014-09-24. 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 extract-gfm versions · Permanent reference to 0.1.0
Package specifications
| Version | 0.1.0 |
|---|---|
| License declaration | Not declared |
| Published | 2014-09-24T03:06:29.360Z |
| 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 | 6 |
| Repository forks | 0 |
Install extract-gfm 0.1.0
npm install extract-gfm@0.1.0 pnpm add extract-gfm@0.1.0 yarn add extract-gfm@0.1.0
Runtime dependencies
- gfm-code-block-regex ^0.2.1
- gfm-code-blocks ^0.2.0
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.
- gfm-code-block-regex@0.2.3 — direct
- gfm-code-blocks@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 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| Code-Review | 0/10 — Found 0/1 approved changesets -- score normalized to 0 |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/extract-gfm/0.1.0 — retrieved 2026-10-29T21:12:39.524Z
- https://api.deps.dev/v3/systems/npm/packages/extract-gfm/versions/0.1.0 — retrieved 2026-10-29T21:12:40.225Z
- https://api.deps.dev/v3/systems/npm/packages/extract-gfm/versions/0.1.0:dependencies — retrieved 2026-10-29T21:12:40.320Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fextract-gfm — retrieved 2026-10-29T21:12:40.525Z