heroui-native-pro@1.0.0-beta.12
HeroUI React Native
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe default install hook performs authenticated network activity and reports a hashed project identifier, while the downloader and endpoint constants are substantially obfuscated. The evidence does not show an unrelated destination or credential exfiltration, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- package.json runs dist/postinstall/index.js automatically after installation.
- The postinstall hook calls HeroUI Pro's CI or CLI artifact downloader when credentials are available.
- The downloader adds a hashed project name to request headers; its endpoint and surrounding behavior are heavily obfuscated.
- The package describes itself as HeroUI React Native, and the hook's stated purpose is to finish installing that product.
- The downloader's project identifier is hashed rather than sent as a readable project name.
- No source evidence establishes that credentials are sent outside the HeroUI service or that the downloaded artifact is unrelated.
Source & flagged code
4 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs dist/postinstall/index.js automatically after installation.
package.jsonView on unpkg · L16Findings
Affected versions and remediation
This report applies to heroui-native-pro@1.0.0-beta.12.
See all versions of heroui-native-pro for other recorded verdicts.
- Review the evidence and your use of heroui-native-pro@1.0.0-beta.12 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.