@skylence-ai/skyline
Content-hash line editor — CLI and MCP server
This report shows the evidence for @skylence-ai/skyline@1.0.73. 9 of 23 known versions are blocked or flagged. The newest version, 1.2.5, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle code concretely performs automatic setup, and package source documents that setup modifies AI-agent CLIs and creates persistent daemon behavior. This meets the firewall block boundary for unconsented postinstall AI-agent control-surface mutation.
Decision evidence
public snapshot- `package.json` registers `postinstall: node postinstall.js`.
- `postinstall.js` automatically runs `bin.js setup` unless CI or `SKYLINE_NO_AUTO_SETUP` is set.
- `bin.js` resolves and executes a platform-specific Skyline binary with the `setup` argument.
- `README.md` states setup installs an autostart daemon and Skyline marketplace plugins for agent CLIs on PATH.
- `README.md` says its Claude plugin uses hooks to steer agents away from built-in Write/Edit/Bash tools.
- No JavaScript source reads credentials, harvests files, or performs network requests.
- The wrapper uses fixed scoped platform-package names and forwards CLI arguments without shell interpolation.
- The lifecycle hook warns on failure rather than retrying or hiding errors.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @skylence-ai/skyline@1.0.73.
The versions list below shows the verdict for each recorded version.
- Avoid installing @skylence-ai/skyline@1.0.73. 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.