← Home

hermes-compiler

npm Repository Homepage

The hermes compiler CLI used during the React Native build process

20
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fbreact-native-botcortinico

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): hermes-compiler exists to distribute prebuilt hermesc binaries and runtime deps (ICU, MSVC). Bundled binaries are its core purpose. ai
npm-metadata suspicious-initial-version AI (npm-metadata): hermes-compiler uses 0.0.0 as a legitimate placeholder version in the React Native/Hermes monorepo publishing workflow by the trusted react-native-bot publisher. ai
bogus-package bogus-package AI (bogus-package): Tiny payload and no deps are consistent with a stub/placeholder package in the Hermes monorepo; published by trusted react-native-bot with 81 versions in registry. ai

Versions (showing 20 of 20)

Version Deps Published
250829098.0.13 0 / 0
250829098.0.12 0 / 0
250829098.0.10 0 / 0
250829098.0.9 0 / 0
250829098.0.8 0 / 0
250829098.0.7 0 / 0
250829098.0.6 0 / 0
250829098.0.5 0 / 0
250829098.0.4 0 / 0
250829098.0.3 0 / 0
250829098.0.2 0 / 0
250829098.0.1 0 / 0
250829098.0.0 0 / 0
0.17.0 0 / 0
0.16.0 0 / 0
0.15.1 0 / 0
0.15.0 0 / 0
0.14.1 0 / 0
0.14.0 0 / 0
0.0.0 0 / 0

v250829098.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.2

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • hermesc/linux64-bin/hermesc

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v250829098.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v250829098.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.