metamask/eth-phishing-detect

0

/ 100

Documentation95
Engineering85
Health94
TypeScript1,293Other1d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Utility for detecting phishing domains targeting Web3 users

Documentation

95

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

85

CI/CD14pt57

CI is configured (.github/workflows/build-test.yml).

Reproducibility6pt80

Lockfile present (yarn.lock). Installs are reproducible.

Tests18pt100

Test files detected (test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Dependency manifest6pt82

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 1,081
    Forks
  • 3
    Releaseslatest 4y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,293
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 28
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/build-test.yml).
    Good: Issue or PR templates present.
  • bin
  • doc
  • src
  • test
    Good: Test files detected (test).
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .prettierrc
  • CONTRIBUTING.md
    Good: 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
  • LICENSE
    Good: Licensed under Other.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: 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.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.