Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real TickTick integration, but its OAuth and endpoint controls could let unsafe configuration or callback input redirect or overwrite account credentials.
Review before installing. Use only with trusted .env and runtime configuration, keep the OAuth and API URLs on official TickTick endpoints, protect the token.json file, and avoid exposing dev/test servers. The publisher should add strong OAuth state validation or PKCE, gate custom endpoints for development only, and update the flagged dev dependencies.
scripts/ticktick-cli.mjs:152OAuth State Is Predictable and Not Validated During Authorization-Code Exchange
");
}
const token = await exchangeCodeAndPersistToken({ code, tokenPath, env });
```
### Technical Analysis
The OAuth `state` p
...[truncated 2212 chars]src/config/ticktick-env.ts:52Configurable OAuth and API Destinations Can Receive TickTick Credentials
vitest 3.2.4 is flagged for arbitrary file read and possible execution when the Vitest UI server is listening, plus the redirect-mock traversal issue. This is a true dependency risk, but it is scoped to testing infrastructure rather than the TickTick OAuth/task runtime; that lowers real-world exposure unless test/UI servers are run in reachable environments.
The manifest resolves vitest to a version with reported critical advisories involving arbitrary file read and possible code execution/path traversal in Vitest components. Even though vitest is a devDependency, it can still be dangerous in developer workstations, CI environments, or any context where the Vitest UI or mocker features are exposed or invoked, potentially compromising source code, secrets, or the build environment.
The declared description describes a substantial TickTick integration toolkit with authentication and operational capabilities. The provided code chunk is only an index file that re-exports another module named 'contract-validation.js'. Based on the supplied code alone, the actual behavior is limited to module export wiring and appears unrelated to TickTick-specific auth or CRUD workflows. This is a material mismatch between the declared purpose and the observed code behavior.
Yes, this is a mismatch based on the supplied code chunk. The declared description describes a full TickTick integration toolkit with authentication, token management, and task/project operations. However, the actual code shown is only a barrel export file that re-exports from an error-categories module. That behavior is materially narrower and unrelated to the declared primary purpose. While this file could be a tiny supporting part of a larger codebase, the evaluation is against the supplied chunk, and this chunk does not implement or indicate the declared capabilities.
Referenced artifact was not completely inspected
| Need OpenClaw action integration | Use `skill-entry/ticktick-skill.mjs` and expose 5 MVP actions |
Referenced artifact was not completely inspected
| Need OpenClaw action integration | Use `skill-entry/ticktick-skill.mjs` and expose 5 MVP actions |
Referenced artifact was not completely inspected
| Need OpenClaw action integration | Use `skill-entry/ticktick-skill.mjs` and expose 5 MVP actions |
Referenced artifact was not completely inspected
| Need OpenClaw action integration | Use `skill-entry/ticktick-skill.mjs` and expose 5 MVP actions |
Referenced artifact was not completely inspected
- `skill-entry/token-manager.mjs`
Referenced artifact was not completely inspected
- `skill-entry/token-manager.mjs`
The skill workflow explicitly loads and refreshes access tokens and may notify via webhook during reauthentication. Handling bearer tokens is inherently sensitive; without strict controls around storage, logging, notification content, and path handling, tokens or authorization state could be exposed and lead to account takeover or persistent API access.
1. Parse env via `parseTickTickEnvFromRuntime`.
2. Resolve token path (`options.tokenPath` -> `TICKTICK_TOKEN_PATH` -> default path).
3. Load access token with auto refresh (`getAccessTokenWithAutoReauth`).
4. On missing/expired token without valid refresh token:
- raise `ReauthRequiredError`
- optionally notify via webhook
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| Category | Typical Source |
|----------|----------------|
| `auth_401` | Invalid/expired access token |
| `auth_403` | Scope/permission denied |
| `not_found_404` | Missing task/project resource |
| `rate_limit_429` | TickTick rate-limited request |
Referenced artifact was not completely inspected
- `src/api/ticktick-api-client.ts`
Referenced artifact was not completely inspected
- `src/api/ticktick-gateway.ts`
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Skill에 주입되는 `getAccessToken()`은 아래 정책으로 운영하는 것을 권장합니다.
1. 메모리/스토리지에서 현재 access token 조회
2. 만료 임박이면 refresh token으로 갱신
3. 갱신 성공 시 저장소 업데이트
4. 실패 시 인증 재진행 요청
nanoid 3.3.11 is flagged for multiple issues involving infinite loops or integer wraparound in generator size handling. In this dependency tree nanoid is transitive via PostCSS, so actual exploitability depends on whether attacker-controlled size values reach vulnerable generator code; the package presence is real, but practical impact in this skill context is less direct than a runtime auth bug.
picomatch 4.0.3 is flagged for method injection and ReDoS issues in glob parsing. Since it is used by dev tooling for file matching, risk is mainly present if untrusted glob patterns are accepted during tooling execution, which is plausible in CI/plugins but not obviously exposed by the lockfile alone.
postcss 8.5.6 is associated with several advisories including arbitrary file read and XSS-related issues. In this repository it appears as a transitive dev-tool dependency under Vite, so the vulnerability is real but most relevant when processing attacker-controlled CSS/config/source map inputs during development or build workflows.
rollup 4.57.1 is flagged for arbitrary file write via path traversal. As a bundler dependency this is principally dangerous during build/dev operations if an attacker can influence archive/module/output paths, which is less severe than a production-facing auth flaw but still meaningful in CI and developer environments.
vite 7.3.1 is reported with multiple high-severity path traversal and arbitrary file read issues affecting the dev server and filesystem protections. Although Vite is a dev dependency, these classes of bugs become serious if a dev server is exposed on a workstation, preview environment, or CI runner, allowing unintended file disclosure from the host.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
parseCallbackUrl,
} from "../skill-entry/token-manager.mjs";
const DEFAULT_ENV_PATH = path.resolve(process.cwd(), ".env");
function printUsage() {
console.log(`TickTick CLI
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
complete-task --taskId <id> [--completedAt <iso>]
Global options:
--env <path> Path to .env (default: ./ .env)
--tokenPath <path> Token JSON path (default: ~/.config/ticktick/token.json)
--help Show help
`);
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
complete-task --taskId <id> [--completedAt <iso>]
Global options:
--env <path> Path to .env (default: ./ .env)
--tokenPath <path> Token JSON path (default: ~/.config/ticktick/token.json)
--help Show help
`);
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
if (reason === "token_file_missing") {
return "Token file is missing. OAuth reauthorization is required.";
}
return "Access token expired or refresh failed. OAuth reauthorization is required.";
}
export function createWebhookReauthNotifierFromEnv(options = {}) {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
if (reason === "token_file_missing") {
return "Token file is missing. OAuth reauthorization is required.";
}
return "Access token expired or refresh failed. OAuth reauthorization is required.";
}
export function createWebhookReauthNotifierFromEnv(options = {}) {