@jive-sh/skill-sync@0.2.3
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall creates login persistence without an explicit install-time consent step, so the package warrants a warning for its background agent setup. The token and user configuration gates, plus the package-aligned sync behavior, do not support a malicious verdict.
Decision evidence
public snapshot- The manifest runs install.cjs automatically after installation, and that script calls registerDaemons during its install path.
- Outside repair-only and CI installs, the installer registers a per-user daemon that can start at login through the platform service manager.
- The daemon exits when no token is configured; its default endpoint is the package’s sync service, and login is an explicit CLI action.
- The runtime detects Claude skill folders and uses the Claude CLI for conflict reconciliation; source and built configuration code show the same integration.
- The daemon does not sync without a configured token, and the CLI obtains that token through an explicit login flow.
- The inspected integration is for syncing Claude skills through the package’s own service; no credential theft or unrelated account action was established.
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.2.3.
See all versions of @jive-sh/skill-sync for other recorded verdicts.
- Review the evidence and your use of @jive-sh/skill-sync@0.2.3 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.