@jive-sh/skill-sync@0.6.1
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe postinstall hook does establish a persistent daemon, but the README clearly describes that behavior as part of skill-sync. Network syncing requires browser passkey sign-in, folder and skill selection governs what is synced, and the reported account usage is disclosed.
Decision evidence
public snapshot- The README discloses that installation registers the package's sync daemon to start at login and that it checks for updates every five minutes.
- Syncing requires a browser passkey sign-in; the service sends a per-machine token directly to the daemon.
- The server controls which skills and folders sync, and folders start disabled until selected.
- Account usage collection is disclosed: the daemon queries the agent CLIs and sends account identity and usage details to the dashboard; the README says it reads no credential files.
- The default service endpoint is skill-sync.jive.sh.
- A postinstall hook runs install.cjs, which registers and starts a persistent daemon by default.
- The daemon reads account usage and supports syncing skill files, so its normal operation accesses and transmits user data.
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.6.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.6.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.