@rubytech/create-sitedesk-code
Install SiteDesk — automated back office for independent building contractors
This report shows the evidence for @rubytech/create-sitedesk-code@0.1.459. 3 of 106 known versions are blocked or flagged. The newest version, 0.1.636, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete AI-agent permission-bypass configuration combined with remote shell bootstrap and persistent system provisioning. Although this is not npm lifecycle execution and uses a brand-scoped directory, the explicit bypass of all Claude permission checks is sufficient for blocking.
Decision evidence
public snapshot- `dist/permissions-seed.js` writes Claude settings with `defaultMode: "bypassPermissions"`.
- The bypass explicitly skips permission checks for every Claude tool.
- `dist/index.js` invokes this settings seed during the CLI install flow.
- The CLI fetches and pipes remote installer scripts to `sh` from Ollama and Astral.
- The installer registers bundled Claude agents/plugins and creates persistent services.
- It installs system packages, copies payloads, and freezes installed source trees.
- `package.json` has no npm preinstall/install/postinstall lifecycle hook.
- The Claude config target is brand-scoped at `~/.sitedesk-code/.claude`, not the default global Claude directory.
- No source-confirmed credential exfiltration endpoint was found in the inspected installer paths.
Source & flagged code
24 flagged · loading sourcePackage contains a possible secret pattern.
payload/platform/scripts/smoke-boot-services.shView on unpkg · L335A single source file combines environment access, network access, and code or shell execution with blocking evidence.
dist/index.jsView on unpkg · L141Findings
Affected versions and remediation
This report applies to @rubytech/create-sitedesk-code@0.1.459.
The versions list below shows the verdict for each recorded version.
- Avoid installing @rubytech/create-sitedesk-code@0.1.459. 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.