0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Utility for detecting phishing domains targeting Web3 users
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
95
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
85
CI is configured (.github/workflows/build-test.yml).
Lockfile present (yarn.lock). Installs are reproducible.
Test files detected (test).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
94
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 1,081Forks
- 3Releaseslatest 4y ago
Community
- -Community health
- -authors own >50% of commits
- 1,293Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 28Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/build-test.yml).Good: Issue or PR templates present.
- bin
- doc
- src
- testGood: Test files detected (test).
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .env.example
- .gitattributes
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- .prettierrc
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- jsconfig.json
- LICENSEGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/metamask/eth-phishing-detect)