hyn-view
Network-first, ultra-low-overhead terminal system monitor for Ubuntu Server. Pure bash, zero runtime dependencies, themeable, with email/push alerting, daily reports, scheduled speed tests and read-only Highway (hw-os) node tracking.
This report shows the evidence for hyn-view@1.8.0. 1 of 11 known versions is blocked or flagged. The newest version, 2.1.0, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package automatically creates root-owned persistence during installation and enables a self-updating execution path. The local-install and cloud-link guards reduce scope but do not neutralize the global-root install behavior.
Decision evidence
public snapshot- The npm lifecycle runs a postinstall script.
- On a global root Linux install, postinstall invokes unattended setup.
- Setup writes system configuration and service units, then enables timers automatically.
- A recurring record timer starts the automatic update check; updates default to install.
- The package persists privileged scheduled execution and can fetch newer releases.
- The lifecycle exits for local installs, non-root installs, and non-systemd hosts.
- Cloud telemetry and portal commands require explicit device linking and a stored token.
- The flagged Python file is a local test mock, not an install-time payload.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe npm lifecycle runs a postinstall script.
package.jsonView on unpkg · L18Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to hyn-view@1.8.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing hyn-view@1.8.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.