@androidand/specsync
Sync OpenSpec changes with work-tracker issues — standalone CLI
This report shows the evidence for @androidand/specsync@0.14.0. 12 of 13 known versions are blocked or flagged. The newest version, 0.14.1, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic postinstall hook writes into multiple foreign global AI-agent directories and installs remotely delivered executable code. That is concrete install-hook abuse under the stated policy.
Decision evidence
public snapshot- The package runs scripts/postinstall.js automatically after installation.
- The postinstall script creates and writes a skill into five global AI-agent skill directories under the user's home directory.
- The installer downloads an executable archive and its checksum from GitHub Releases, then installs the extracted executable.
- The CLI launcher executes that downloaded binary.
- The installer downloads a release archive and checksum from GitHub, verifies its SHA-256 hash, then extracts it.
- The CLI runs the platform binary that the postinstall step downloaded.
- The archive checksum is checked before extraction.
- No source code reads environment variables or uploads local files.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
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 @androidand/specsync@0.14.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @androidand/specsync@0.14.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.