@react-native-ohos/react-native-ssl-pinning MIT 2 versions

@react-native-ohos/react-native-ssl-pinning

npm Repository Homepage

React Native module for harmony

Versions

MIT

License

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

hdjkerchenhaoyuelongzilouis-c7tangshutongleehom1129abilitqin666wangyuedddqh0334fankwxinggenglzm_rnnathan_xinxintopding_chengjienpmywpwenhuichen133

Keywords

react-native

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Inflated semver tracks upstream version; sparse README is typical for OpenHarmony SIG platform wrappers.	ai	2026/05/06
phantom-deps	phantom-dep:react-native-ssl-pinning	AI (phantom-deps): Platform-specific alias wrapper; react-native-ssl-pinning is intentionally declared but not directly imported.	ai	2026/05/06
dependencies	unvetted-dep:react-native-ssl-pinning	AI (dependencies): Expected peer dependency for this HarmonyOS wrapper package; not a novel or suspicious addition.	ai	2026/05/06

Versions (showing 2 of 2)

Version	Deps	Published
1.6.0	2 / 0	2026-03-26
1.5.8	2 / 0	2026-03-26

v1.6.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.

v1.5.8

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.