# Folder / Repo Inspection Report Template

Use this when someone sends a folder, repo, tool pack, or downloaded project and asks:

> Is this useful? Is it safe? What should I do with it?

## 1. Verdict

Choose one:

- Keep and use
- Keep as reference only
- Needs cleanup before use
- Not useful for the current goal
- Risky, do not run yet

Short verdict:

> [Write 2-3 plain-language sentences.]

## 2. What Is Inside

| Area | What it contains | Notes |
| --- | --- | --- |
| Root files |  |  |
| Source code |  |  |
| Docs |  |  |
| Config |  |  |
| Tests |  |  |
| Data/assets |  |  |

## 3. What Works

- 
- 
- 

## 4. What Is Missing

- Setup instructions
- Tests
- Example inputs
- Environment variables
- Payment or API key instructions
- License
- Security notes

## 5. Risks

Check for:

- Hardcoded secrets
- Unknown scripts
- Auto-delete behavior
- Network calls
- Payment/crypto behavior
- Browser extension permissions
- Unclear data handling

## 6. Recommended Next Step

Pick one:

- Publish as-is
- Add README first
- Run local smoke test
- Remove risky files
- Turn into a template
- Archive and ignore

## 7. Paid Help CTA

Mary Wang can inspect a messy folder/repo and turn it into a plain-language report plus next steps.

Email: [939172168@qq.com](mailto:939172168@qq.com)