@jive-sh/skill-sync@0.5.1
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install hook sets up the package's own daemon, which the README describes. Network syncing requires an explicitly obtained machine token and applies only to selected skills; no malicious behavior was identified.
Decision evidence
public snapshot- The README says sign-in uses a passkey and the service issues a per-machine token to the daemon.
- The README discloses that installation registers the package's own daemon to start at login and that it automatically updates.
- The daemon resumes syncing only when a saved token exists; otherwise it stays signed out.
- Sync operations are limited to skills on the synced list; other skills are never pushed, overwritten, or deleted.
- The postinstall hook registers and starts a persistent daemon, and the daemon automatically upgrades itself; both behaviors are disclosed and serve the package's stated purpose.
Source & flagged code
7 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.5.1.
See all versions of @jive-sh/skill-sync for other recorded verdicts.
- Review the evidence and your use of @jive-sh/skill-sync@0.5.1 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.