Audit should work on monorepos
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Audit commands assume a single project at the repo root. In a monorepo with multiple apps/packages, the audit should detect the relevant sub-projects and audit each (or let the user pick) rather than only scanning the root or failing to find an integration. Today it doesn't handle the monorepo layout.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the audit command entry point and the project-discovery logic, then inspect how root-level integrations are detected. Done means a monorepo's relevant sub-projects are audited individually or presented for selection without breaking single-project repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100