0
/ 100
Getting noticed, but rough fundamentals could turn visitors away.
Institutional-grade web3 security.
Documentation
0
No README found in the repository.
→ Add a README.md describing what the project does, how to install it, and how to run it.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
Engineering
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Project health
48
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 37Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 333Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files67 root entries
- 246 Club
- AbracadabraMoney
- Ambit
- Animecoin
- Aria
- BaselineMarkets
- BeefyFinance
- Bounce
- Bracket
- Bridges
- BTCX
- Cyfrin
- Degen Safe
- DN404
- Dolomite
- eGMX
- Ethena
- Ethereal
- FastLane Labs
- Foil
- G8keep
- GammaStrategies
- GMX
- Impermax
- IVX
- Jupiter
- K33Loans
- KeyFinance
- LayerZero
- M0
- Magna
- MagnifyCash
- Manifest
- MIMSwap
- MUX
- Nashpoint
- NFTR
- Norlend
- Nunchi
- Olympus
- Orderly
- PariFi
- Peapods
- PleasR
- Poolshark
- Reflex Protocol
- Reliquary
- RestFinance
- Sentiment
- Sentry
- Smardex
- Strata
- Synthetix
- Tenor
- Trueo
- UltiBets
- Umami
- Universal
- USDT0
- Valantis
- Yellow Network
- YugaLabs
- Zap
- HamstersOfOpera_Guardian_Audit.pdf
- IceBearSociety_Audit.pdf
- InfinityLotto_Audit.pdf
- UltimateFantoms_Audit.pdf