@jive-sh/skill-sync@0.4.13
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s stated sync behavior and sign-in flow are consistent with its purpose, and the usage reporting is disclosed. However, it automatically sends account-linked usage and cost information during a signed-in session, with no usage-specific opt-out found, so this merits a telemetry warning.
Decision evidence
public snapshot- After a user signs in, the daemon reads usage data for every detected Claude and Codex account and sends it over its service connection.
- Usage reports include account identifiers and usage or cost figures, and are sent when changed and periodically while connected.
- The README discloses this reporting, but no usage-specific opt-out appears in the inspected source.
- The daemon’s service connection is gated on an active signed-in session; sign-in is an explicit CLI action.
- The package documents its postinstall daemon registration and automatic startup as part of the sync service.
- The README says only selected skills sync, and newly detected folders start with syncing off.
- The usage reader extracts usage figures from tool-written files; the inspected flow does not send credentials or session contents.
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.4.13.
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.13 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.