@jive-sh/skill-sync@0.4.11
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe postinstall hook creates user-level startup persistence and launches the daemon without an affirmative consent check. This is a concrete residual risk, but the inspected source does not establish malicious collection or other attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package with lifecycle scripts enabled, except when CI is set.
Impact
The daemon continues running across logins without a separate setup command, while its runtime behavior remains unresolved from the inspected source.
Mechanism
The installer writes and enables a user-level startup entry on supported platforms, then starts the daemon.
AI rationale
The postinstall hook creates user-level startup persistence and launches the daemon without an affirmative consent check. This is a concrete residual risk, but the inspected source does not establish malicious collection or other attack behavior.
Evidence
package.jsoninstall.cjs
Decision evidence
public snapshotAI called this Suspicious at 79.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs install.cjs automatically during postinstall.
- The installer registers a daemon to start at login and starts or restarts it immediately; the only shown skips are repair-only mode and CI.
- The available source does not resolve the daemon’s runtime behavior, so the automatic persistence remains a concrete unresolved risk.
Evidence against
- The package describes the daemon as part of its skill synchronization product, and the installer visibly logs registration activity.
- The inspected source does not establish credential collection, data exfiltration, or destructive behavior.
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.11.
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.11 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.