@jive-sh/skill-sync@0.4.7
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe postinstall hook creates persistent user-session startup behavior, and platform package sources remain unresolved. The inspected JavaScript does not establish a concrete attack, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package outside CI and without the repair-only flag.
Impact
The daemon can continue running across logins until it is stopped or its registration is removed.
Mechanism
The installer registers the daemon with the operating system’s user-session startup manager and enables or restarts it.
AI rationale
The postinstall hook creates persistent user-session startup behavior, and platform package sources remain unresolved. The inspected JavaScript does not establish a concrete attack, so this warrants a warning rather than a block.
Evidence
package.jsoninstall.cjssrc/daemons/skill-sync-daemon.ts
Decision evidence
public snapshotAI called this Suspicious at 77.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs install.cjs automatically after installation and declares platform aliases that resolve to versioned releases of the same package.
- install.cjs repairs command targets and registers the daemon during installation; on Linux it enables and restarts a user systemd unit.
- The daemon registration is skipped in CI or when passed a repair-only flag, but otherwise the installer registers its declared daemon.
- The source describes the daemon as maintaining a connection to the service hub; the CLI provides a logout command that revokes the machine token and stops syncing.
Evidence against
- The inspected source describes the daemon’s role as syncing selected skills through the service hub, and provides a logout path to revoke its token.
- The platform-specific package sources could not be fully resolved in this snapshot, so their executable behavior remains unverified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.7.
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.7 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.