fix(security): isolate saleable readiness subprocess authority - #107
Conversation
|
Warning Review limit reached
Next review available in: 43 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughReadiness 하위 프로세스는 전체 ChangesReadiness 환경 변수 제한
Estimated code review effort: 3 (Moderate) | ~20 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/saleable-readiness-audit.mjs`:
- Around line 16-41: Allow the explicit NOEMA_AUDIT_REPORT_ONLY override to
reach child processes by adding it to readinessSubprocessEnvironmentKeys in
scripts/saleable-readiness-audit.mjs; preserve the existing filtering that
blocks ambient inheritance. Update
test/saleable-readiness-subprocess-environment.test.ts in the required allowlist
contract to include this key.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 91d49c62-b54a-4a1a-bdce-c62f49abb032
📒 Files selected for processing (2)
scripts/saleable-readiness-audit.mjstest/saleable-readiness-subprocess-environment.test.ts
Test-first hardening of the saleable-readiness subprocess authority boundary, non-destructively refreshed onto protected
main18cac8dcab31dd53048d5d14ad01673b5b77d141. No predecessor checks, reviews, scanner/model output, production KPI/smoke evidence, release evidence, or acquisition evidence transfer after refresh.RCA -> RED -> GREEN -> review repair
Protected
scripts/saleable-readiness-audit.mjsforwarded the complete ambient environment into nested npm, security, KPI, alert, and smoke subprocesses. The RED contract required an explicit behavior-level allowlist. GREEN introducedcreateReadinessSubprocessEnvironment()with only platform launch/TLS/locale plus bounded KPI/alert/smoke configuration.CodeRabbit then identified a valid functional regression: the allowlist removed an explicitly supplied
NOEMA_AUDIT_REPORT_ONLYoverride even thoughrunCommand()distinguishes that explicit override from ambient inheritance. REDa7edd13128642de578e928293e326ba4b895b477pinned the override contract and GREENc913196f51f2cf85ef33129cb1cecdc409a664edadded only that reviewed key while retaining ambient-value deletion. The sole inline finding is resolved.Current exact source
Current head
091cb6cdec07330dc10a2eae772103ea57af2c4fis a non-forced refresh preserving OpenAPI-integrated protected main plus the exact reviewed final blobs:scripts/saleable-readiness-audit.mjs0054030f6e66d2211195bfc545f14980f04e9966;test/saleable-readiness-subprocess-environment.test.ts0bc3cfdc95a295605ee324db6c8e77597e7a2242.Fresh diff contains only those two paths and is zero commits behind the observed protected base. The visible formal review remains
COMMENTEDon a predecessor; current unresolved inline threads are zero.Exact-head evidence
For unchanged head
091cb6cdec07330dc10a2eae772103ea57af2c4f:ci31595905471: queued/non-passing at the latest direct run read;31595905416: queued/non-passing;Security Scan31595905266: queued/non-passing.The PR remains Draft until the unchanged exact head has terminal-success applicable gates and current findings remain clean. No blind rerun, clean-head churn, synthetic status, or gate weakening is used.
Authority boundary
This repair narrows local child-process authority only. It does not create real KPI/smoke evidence, prove saleability, publish a release, deploy Noema, choose an outbound license, establish revenue/legal/IP-transfer evidence, or create acquisition readiness.