@react-native-community/cli-hermes MIT 19 versions

@react-native-community/cli-hermes

npm Repository Homepage

This package is part of the [React Native CLI](../../README.md). It contains commands for managing the Hermes engine.

19

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dmitryrykunsafaiyehcortinicolunaleapsbartoszklonowskititozzzempyricalcpojermattoakesferrannpmike866krizzutrensikthymikeenicholaslee119mmazzarolorewieerjanicduplessisswaagiekelsetjohandutoitvonovakwojteg1337naturalclarconnectdotzpvinisbrentvatneevanbaconeliwhitealloy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:chalk	AI (phantom-deps): chalk is explicitly declared as a direct dependency in package.json; the phantom-dep finding is a false positive for this package.	ai	2026/04/26

Versions (showing 19 of 19)

Version	Deps	Published
13.6.9	4 / 2	2024-06-05
13.6.8	4 / 2	2024-06-03
13.6.7	4 / 2	2024-06-03
13.6.6	4 / 2	2024-04-25
13.6.5	4 / 2	2024-04-18
13.6.4	4 / 2	2024-03-27
13.6.3	4 / 2	2024-03-20
13.6.2	4 / 2	2024-03-11
13.6.1	4 / 2	2024-02-22
13.6.0	4 / 2	2024-02-19
13.5.2	5 / 2	2024-02-05
13.5.1	5 / 2	2024-01-23
13.5.0	5 / 2	2024-01-15
13.4.0	5 / 2	2024-01-08
13.3.0	5 / 2	2024-01-08
13.2.0	5 / 2	2023-12-22
13.1.0	5 / 2	2023-12-13
13.0.1	5 / 2	2023-12-11
13.0.0	5 / 2	2023-12-04

v13.6.8

1 finding

LOW No provenance attestation provenance

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

v13.6.7

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.

v13.6.6

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.

v13.6.5

1 finding

LOW No provenance attestation provenance

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

v13.6.4

1 finding

LOW No provenance attestation provenance

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

v13.6.3

1 finding

LOW No provenance attestation provenance

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

v13.6.2

1 finding

LOW No provenance attestation provenance

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

v13.6.1

1 finding

LOW No provenance attestation provenance

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

v13.6.0

1 finding

LOW No provenance attestation provenance

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

v13.5.2

1 finding

LOW No provenance attestation provenance

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

v13.5.1

1 finding

LOW No provenance attestation provenance

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

v13.5.0

1 finding

LOW No provenance attestation provenance

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

v13.4.0

1 finding

LOW No provenance attestation provenance

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

v13.3.0

1 finding

LOW No provenance attestation provenance

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

v13.2.0

1 finding

LOW No provenance attestation provenance

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

v13.1.0

1 finding

LOW No provenance attestation provenance

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

v13.0.1

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.

v13.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.