@jive-sh/skill-sync@0.4.14
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe postinstall hook installs a login daemon, a consequential behavior that the README clearly describes. The daemon waits for explicit sign-in before syncing, limits file synchronization to selected skills, and sends requests to the configured service endpoint.
Decision evidence
public snapshot- The postinstall hook runs install.cjs, which repairs command targets and registers the package daemon.
- The README discloses that installation registers the daemon to start at login and that it checks for package updates every five minutes.
- At daemon startup, syncing resumes only if a saved token exists; otherwise it waits for the user to sign in with skill-sync login.
- Sync code filters to selected skills, and requests use the configured skill-sync service endpoint.
- Postinstall creates login persistence and starts the daemon, so installation has an automatic side effect.
- The daemon can install updates through the package manager without a separate update command; this behavior is documented.
Source & flagged code
6 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @jive-sh/skill-sync@0.4.14.
See all versions of @jive-sh/skill-sync for other recorded verdicts.
- Review the evidence and your use of @jive-sh/skill-sync@0.4.14 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.