@jive-sh/skill-sync@0.4.15
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe postinstall hook configures a persistent daemon, but the package documents that behavior as necessary for syncing and updating. The inspected source sends skill data and disclosed usage readings to its configured service; no unrelated credential collection or other attack behavior was found.
Decision evidence
public snapshot- The postinstall hook installs command targets and registers the package’s daemon; the README discloses that it starts at login.
- The daemon syncs skills to the documented skill-sync service, and network requests use the configured endpoint with the service token.
- File uploads are limited to skill files selected for sync; account usage is described as readings from Claude and Codex usage files.
- Installation creates a login-starting daemon and the README says it automatically checks for updates every five minutes.
- The platform-specific executable packages were unavailable for direct source inspection.
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.4.15.
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.15 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.