@react-native-oh/react-native-harmony-cli No license 20 versions

@react-native-oh/react-native-harmony-cli

npm

20

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

liu_wentaoyujunsongfxyyf1998xieyifenghuabenbenzicionliyiqunjf_huadjt123

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:adm-zip	AI (phantom-deps): adm-zip is directly imported in source; false positive from config-file heuristic.	ai	2026/05/26
phantom-deps	phantom-dep:@tsconfig/recommended	AI (phantom-deps): @tsconfig/recommended is a legitimate TypeScript config dependency; false positive.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Sparse README and empty keywords are documentation gaps, not malware indicators; stable for this package.	ai	2026/05/26
semgrep	semgrep:silent-process-exec	AI (semgrep): Detached spawn is used to launch an emulator process — expected CLI behavior, not a reverse shell.	ai	2026/04/30
semgrep	semgrep:silent-process-exec-var	AI (semgrep): Same emulator-launch spawn; variable path is user-supplied emulator executable, not attacker-controlled.	ai	2026/04/30
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads a user-specified template config file — standard CLI scaffolding pattern.	ai	2026/04/30

Versions (showing 20 of 20)

Version	Deps	Published
0.84.1	14 / 14	2026-06-08
0.82.31	14 / 14	2026-06-08
0.82.30	14 / 14	2026-05-21
0.82.23	14 / 14	2026-04-15
0.82.7	13 / 14	2026-01-28
0.77.72	14 / 14	2026-06-05
0.77.71	14 / 14	2026-05-21
0.77.64	14 / 14	2026-04-15
0.77.44	13 / 14	2026-01-22
0.77.40	13 / 14	2026-01-06
0.77.33	13 / 14	2025-11-21
0.77.22	13 / 14	2025-09-29
0.77.18	13 / 14	2025-08-29
0.72.141	18 / 16	2026-06-05
0.72.140	18 / 16	2026-05-21
0.0.43	18 / 16	2026-04-15
0.0.40	17 / 16	2025-11-21
0.0.37	17 / 16	2025-09-09
0.0.36	17 / 16	2025-08-25
0.0.30	14 / 15	2025-06-10

v0.84.1

1 finding

LOW No provenance attestation provenance

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

v0.82.31

1 finding

LOW No provenance attestation provenance

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

v0.82.30

1 finding

LOW No provenance attestation provenance

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

v0.82.23

1 finding

LOW No provenance attestation provenance

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

v0.82.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.

v0.77.72

1 finding

LOW No provenance attestation provenance

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

v0.77.71

1 finding

LOW No provenance attestation provenance

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

v0.77.64

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.

v0.77.44

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.

v0.77.40

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.

v0.77.33

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.

v0.77.22

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.

v0.77.18

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.

v0.72.141

1 finding

LOW No provenance attestation provenance

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

v0.72.140

1 finding

LOW No provenance attestation provenance

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

v0.0.43

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.

v0.0.40

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.

v0.0.37

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.

v0.0.36

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.

v0.0.30

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.