@brainervirus/workit-opencode@1.0.12
Workit OpenCode plugin — native tools, adaptive policy, and fourteen method skills
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe inspected source supports ordinary workflow-plugin behavior, with no install hooks, self-dependency chain, or concrete covert attack. Scanner signals arise from repository commands, configured service authentication, and expected host integration.
Decision evidence
public snapshot- package.json has only build and typecheck scripts, with no install lifecycle hooks or runtime self-dependency.
- The active plugin registers Workit workflow tools and an initialization tool.
- Command execution uses executable arguments and a repository working directory without enabling a shell.
- YouTrack requests use a token file and service endpoint supplied through configuration; no unrelated credential harvesting was identified.
- Active workflow tools require host session observation and matching workspace identity.
- The host configuration callback adds workflow restrictions, including denying direct Git worktree commands.
Source & flagged code
5 flagged · loading sourceSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/plugin.jsView on unpkg · L21Findings
Affected versions and remediation
This report applies to @brainervirus/workit-opencode@1.0.12.
See all versions of @brainervirus/workit-opencode for other recorded verdicts.
- Review the evidence and your use of @brainervirus/workit-opencode@1.0.12 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.