@jive-sh/skill-sync@0.6.0
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe postinstall hook establishes the package’s own sync daemon, and the README discloses login startup and automatic updates. The inspected source ties service requests and usage reporting to the sync/dashboard features and user sign-in; no unrelated collection or unauthorized action was found.
Decision evidence
public snapshot- The package syncs selected skills through its Jive service after the user signs in; the daemon uses a per-machine token.
- The README discloses that installation registers the sync daemon to start at login and that it checks for updates every five minutes.
- The daemon reports account identity, plan limits, and local usage for the dashboard; its source says it does not read or send provider credentials.
- Sync code limits file operations to skills on the synced list; other skills are not pushed, overwritten, or deleted.
- A postinstall script runs automatically and can register a persistent login daemon.
- The daemon automatically upgrades itself and sends account usage data to the service when it changes.
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.0.
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.0 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.