registry / @jive-sh/skill-sync / 0.4.16
@jive-sh/skill-sync@0.4.16
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe postinstall does create user-level login persistence, but the README clearly describes this behavior and it directly supports the package's sync-daemon purpose. Network syncing requires browser sign-in and is limited to skills selected through the dashboard.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs postinstall; the daemon connects after a user signs in.
Impact
The daemon persists across logins and can sync selected skill files to the configured service as described by the package.
Mechanism
The installer registers the package's daemon with the platform's user-session service. The daemon syncs dashboard-selected skills using the user's machine token.
AI rationale
The postinstall does create user-level login persistence, but the README clearly describes this behavior and it directly supports the package's sync-daemon purpose. Network syncing requires browser sign-in and is limited to skills selected through the dashboard.
Evidence
~/.jive/daemons~/.jive/logs~/Library/LaunchAgents$XDG_CONFIG_HOME/systemd/user~/.jive/skill-sync-token.jsondetected skills folders
Network endpoints1
skill-sync.jive.sh
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall script repairs the package's CLI targets and registers its own sync daemon.
- The README discloses that the daemon starts at login after installation and upgrades through the package manager.
- Sync requires a token supplied through browser sign-in, and only skills selected on the dashboard are synced.
- The default service endpoint is https://skill-sync.jive.sh, and requests send the signed-in machine token to the configured endpoint.
- The sync code documents that unselected skills are never pushed, overwritten or deleted.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = node ./install.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./install.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkginstall.cjsView file
3Manifest entrypoint (scripts.postinstall) carries capability families absent from dist/build output: environment+network, execution+network
L3: // CommonJS, not an ES module: a launcher is an extensionless file, and Node 14 and 16 refuse to load an
L4: // extensionless ES module in a "type": "module" package (ERR_UNKNOWN_FILE_EXTENSION; Node 18.20 accepts it). bin/package.json marks this directory
L5: // "commonjs", and the install script is install.cjs, so both load the same way on every Node and on Bun.
L6: const { spawnSync } = require("child_process");
L7: const {
...
L81: const packageJsonPath = require.resolve(`${PLATFORM_PACKAGES[platformKey]}/package.json`);
L82: const packageJson = JSON.parse(readFileSync(packageJsonPath, "utf-8"));
L83: return {
...
L97: * package manager: on an
Findings
4 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighEntrypoint Build Divergenceinstall.cjs
HighTrigger Reachable Persistenceinstall.cjs
HighSemantic Analysis Limitedbin/skill-sync#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistenceinstall.cjs
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @jive-sh/skill-sync@0.4.16.
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.16 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.