Security fixes target the current main branch and the latest v0.2.x release.

Report vulnerabilities through the repository's private security advisory form. If that form is unavailable, open a minimal issue asking the maintainer to contact you without including exploit details, credentials, or private data.

Do not include live Dida365 cookies, bearer tokens, private task exports, or full response dumps in public issues.

We aim to acknowledge reports within 3 business days and complete initial triage within 7 business days. Fix and coordinated disclosure will usually occur within 90 days; reports may be disclosed earlier when a mutually tested fix is available. Active exploitation or exposed credentials will be handled as an immediate containment incident.

Last reviewed: 2026-10-23.

• Go dependency surface: standard library only; go.mod is the version source.
• npm package: no runtime dependencies.
• GitHub Actions: pinned to full commit SHAs with release comments.
• Required pull-request checks: tests, vet, Staticcheck, govulncheck, private-state scan, CodeQL, and agent-plugin manifest validation. OpenSSF Scorecard runs on main and on a schedule.
• main rejects force pushes and deletion, requires linear history, and requires the pull-request checks above. While the project has one active maintainer, pull requests use agent-assisted review rather than a second human approval.
• Release publication: tag-triggered only after make release-check VERSION=....

The update cadence, CVE response targets, release gates, and trust boundaries are defined in docs/security/dependency-and-release-policy.md.

DidaCLI stores credentials under ~/.dida-cli/ and redacts token previews in CLI output. The repository ignores local env files, private data, and generated binaries.

Agents and scripts should import cookies through stdin or browser capture. They should never ask users to paste secrets into chat.

The bundled Codex/Claude Code plugin declares the official remote Dida365 MCP server but does not bundle credentials or a local privileged executable. Plugin writes still go through the host's approval UI and DidaCLI's own --dry-run/--yes boundaries.