hermes-compiler 0.14.0-commitly-202510291325-4439b57dd

The hermes compiler CLI used during the React Native build process

hermes-compiler@0.14.0-commitly-202510291325-4439b57dd was published on 2025-10-29. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All hermes-compiler versions · Permanent reference to 0.14.0-commitly-202510291325-4439b57dd · Latest release

Package specifications

Version0.14.0-commitly-202510291325-4439b57dd
License declarationMIT
Published2025-10-29T13:46:26.561Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size43690.86 KiB
Published file count15
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars11385
Repository forks886

Install hermes-compiler 0.14.0-commitly-202510291325-4439b57dd

npm install hermes-compiler@0.14.0-commitly-202510291325-4439b57dd
pnpm add hermes-compiler@0.14.0-commitly-202510291325-4439b57dd
yarn add hermes-compiler@0.14.0-commitly-202510291325-4439b57dd

Runtime dependencies

  • None declared

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-Review10/10 — all changesets reviewed
    Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    License10/10 — license file detected
    Security-Policy9/10 — security policy file detected
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Signed-Releases0/10 — Project has not signed or included provenance with any releases.
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    SAST0/10 — no SAST tool detected
    Binary-Artifacts9/10 — binaries present in source code
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    Fuzzing10/10 — project is fuzzed

    Evidence and freshness