release: v0.1.6

[ajianaz]

v0.1.6 Release

Added

• Custom system prompts via .cora.yaml config (feat: Custom system prompt via .cora.yaml config #94)
• response_format: json_object opt-in (feat: Add json_object response format (opt-in) #92)
• File path injection into review prompts (feat: Inject valid file paths into system prompt #93)
• Post-parse file path filtering (feat: Inject valid file paths into system prompt #93)
• Enhanced default system prompts with anti-hallucination constraints (feat: Enhanced default system prompts #95)

Fixed

• Path traversal in system_prompt_file (feat: Add json_object response format (opt-in) #92)
• Symlink bypass in path traversal guard

Stats

• 178 tests passing
• Clippy clean
• Format clean
• Cora self-review: no issues

[coderabbitai]

Warning

Review limit reached

@ajianaz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes and 14 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7348bc6e-c693-4357-92ce-d0720d88cbdd

📥 Commits

Reviewing files that changed from the base of the PR and between 46ce8d2 and 946ba8a.

📒 Files selected for processing (7)

• CHANGELOG.md
• Cargo.toml
• README.md
• src/commands/scan.rs
• src/config/schema.rs
• src/engine/llm.rs
• src/engine/review.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.1.6

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🔍 Cora AI Code Review

❌ Blocked — critical issues found.

🔴 Error (3)

• src/engine/review.rs:12 — The load_system_prompt_file function uses std::env::current_dir() to determine the project root. This is the process working directory, which may not be the actual project root (e.g., if the CLI is invoked from a subdirectory, or the working directory changes). The canonicalized path comparison could allow or deny files incorrectly. The project root should be explicitly passed in or derived from the config file location.
• src/engine/review.rs:18 — While the code canonicalizes both the file path and the project root, a symlink inside the project root pointing outside would pass the starts_with check since the symlink itself is inside the project. However, canonicalize resolves the symlink, so the resolved target could be outside the project root. Wait — actually canonicalize on the file path resolves symlinks, so if a symlink inside the project points to /etc/passwd, canonical would be /etc/passwd which does NOT start with project_root. So this is actually fine. BUT: the reverse is also a concern — if the project root itself contains a symlink, canonicalize(&project_root) resolves it, but canonicalize(path) also resolves, so the comparison is consistent. This is actually handled correctly.

However, there's a TOCTOU issue: the canonicalization and the read happen at different times. An attacker could replace a valid file with a symlink between the check and the read.

• src/engine/review.rs:261 — The is_valid_file_path function uses exact string comparison. LLMs may return file paths with slight variations (e.g., leading ./, different path separators, or relative vs absolute). This could cause legitimate issues to be filtered out. For example, the diff might contain src/main.rs but the LLM returns ./src/main.rs or src\main.rs on Windows.

---

Review powered by cora-cli · BYOK · MIT