thorta
OpenCode preconfigured with the THORTA development environment, agents, and skills
This report shows the evidence for thorta@1.0.4, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThis matches the blockable policy for unconsented lifecycle mutation of foreign or broad AI-agent control surfaces, even though the content appears package-aligned and no exfiltration endpoint was found. The behavior is install-triggered, persistent in user config locations, and affects agent instruction/control files outside the package.
Decision evidence
public snapshot- package.json runs node bin/cli.js --sync on both install and postinstall.
- bin/cli.js main() always rewrites cwd opencode.json and may rename ~/opencode.json during lifecycle.
- bin/cli.js syncSkillsAndRules writes package SKILL.md files into ~/.config/opencode and ~/.opencode.
- bin/cli.js writes AGENTS.md and CLAUDE.md into ~/.config/opencode and ~/.opencode with package-supplied agent instructions.
- Generated OpenCode config grants bash/write/edit tools and disables default build/plan agents when CLI launches.
- No external network endpoints or credential exfiltration found in inspected files.
- Agent/build scripts appear user-invoked after CLI run, not lifecycle-triggered by --sync.
- Writes target OpenCode-related locations rather than arbitrary shell startup or OS persistence files.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
bin/cli.jsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dev-server.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to thorta@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing thorta@1.0.4. 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.