zentao-api-old
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This looks like a real ZenTao integration, but it exposes broad credentialed admin/raw API powers and persistent sessions that users should review carefully before installing.
Install only if you intend to let the agent use a ZenTao account. Use a least-privileged account, do not provide admin credentials for routine work, require confirmation for delete/batch/admin/API-key/SQL/debug actions, and clear the .zentao/sessions directory when finished.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A connected agent could potentially run broad ZenTao module actions or SQL queries instead of only performing the project-management task the user intended.
These are broad raw API/SQL-style escape hatches, not narrow project/task/bug workflows. If an agent uses them with ZenTao credentials, it could bypass safer scoped operations.
`/api-getModel-[moduleName]-[methodName]-[params].json` ... `执行指定模块的方法并返回结果`; `/api-sql-[keyField].json` ... `执行SQL查询`
Remove or disable raw/debug/SQL-style endpoints from agent-facing guidance, or require explicit user confirmation and least-privileged ZenTao accounts before any such call.
If used with an account that has admin rights, the agent could change user-group permissions and affect other users' access.
The skill bundle documents privilege-management actions. That administrative authority exceeds ordinary project/task/bug management unless tightly scoped to an admin use case.
`/group-managePriv-[groupID].json` ... `描述 | 管理用户组权限`
Use a least-privileged ZenTao account for routine task/bug/project work, and require explicit confirmation before any permission, user, group, API-key, extension, or admin operation.
Anyone or any process with access to the local session files may be able to reuse authenticated ZenTao access until the session is cleared or expires.
ZenTao username/password use and local session persistence are expected for this integration, but they are sensitive and reusable.
`credentials = read_credentials()` ... `credentials['username'], credentials['password']` ... `存储位置：项目根目录 .zentao/sessions/`
Store TOOLS.md and .zentao/sessions securely, avoid admin credentials when possible, and clear sessions after sensitive work.
Users have less external context for who maintains the skill and where to audit updates.
The package provenance is limited. This is not evidence of malicious behavior, but it reduces independent verifiability.
Source: unknown; Homepage: none
Prefer installing after reviewing the included code and pinning trusted versions, especially because the skill can use ZenTao credentials.