registry / @jive-sh/skill-sync / 0.4.9
@jive-sh/skill-sync@0.4.9
Keeps one skills directory identical across every machine you work on.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest combines a postinstall hook with platform-specific self-alias dependencies whose source is unresolved. The inspected installer and runtime show package-aligned setup and syncing, but they do not resolve the nested release behavior, so a warning is appropriate.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package with npm on a supported platform.
Impact
The unresolved nested release lifecycle leaves a supply-chain risk that cannot be assessed from the available source.
Mechanism
The postinstall runs install.cjs, while platform-specific optional dependencies select releases of the same package; those releases may have their own install lifecycle.
AI rationale
The manifest combines a postinstall hook with platform-specific self-alias dependencies whose source is unresolved. The inspected installer and runtime show package-aligned setup and syncing, but they do not resolve the nested release behavior, so a warning is appropriate.
Evidence
package.jsoninstall.cjs
Decision evidence
public snapshotAI called this Suspicious at 79.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- package.json runs install.cjs during postinstall and declares optional dependencies that alias back to this package at platform-specific release versions.
- The platform package source is unresolved, so its lifecycle behavior and payload could not be verified.
Evidence against
- The inspected installer repairs command targets and registers the package’s own daemon; the inspected daemon and server code describe syncing through the configured service.
- No concrete malicious behavior was established in the inspected source.
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.9.
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.9 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.