@mapbox/babel-plugin-transform-jsxtreme-markdown 0.5.0

Transform Markdown interpolated with JS expressions and JSX elements at compile time

@mapbox/babel-plugin-transform-jsxtreme-markdown@0.5.0 was published on 2018-04-10. 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 >=4.

All @mapbox/babel-plugin-transform-jsxtreme-markdown versions · Permanent reference to 0.5.0 · Latest release

Package specifications

Version0.5.0
License declarationMIT
Published2018-04-10T16:27:03.327Z
Node.js requirement>=4
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.38 KiB
Published file count8
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies241
Repository stars92
Repository forks8

Install @mapbox/babel-plugin-transform-jsxtreme-markdown 0.5.0

npm install @mapbox/babel-plugin-transform-jsxtreme-markdown@0.5.0
pnpm add @mapbox/babel-plugin-transform-jsxtreme-markdown@0.5.0
yarn add @mapbox/babel-plugin-transform-jsxtreme-markdown@0.5.0

Runtime dependencies

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.

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.

Code-Review3/10 — Found 6/17 approved changesets -- score normalized to 3
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness