yadavnikhil17102004/cve-intel

0

/ 100

Documentation73
Engineering38
Health100
HTML271d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Native Go engine for automated aggregation, sanitization, and JSON-exporting of global CVE exploit Proof-of-Concepts. Continuously mirrored from the wild

Documentation

73

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

Engineering

38

Issue and PR templates6pt0

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.

Reproducibility6pt5

No dependency lockfile found (−70 pts).

→ Commit go.sum so Go module downloads are repeatable.

Tests18pt30

Go module found but no *_test.go files detected.

→ Add *_test.go files alongside your packages and run `go test ./...`.

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Formatting enforced (gofmt (built into Go toolchain)).

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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)
  • 7
    Forks
  • 2
    Releaseslatest 5d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 27
    Watchers

Responsiveness

  • —
    Median issue response
  • 36d 22h
    Median PR merge time
  • 6
    Open issues
Repository files26 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • assets
  • data
  • docs
  • sample-data
  • web
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .nojekyll
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
    Good: Contributing guide includes code examples.
  • cvemapping.go
  • cvemapping.sh
  • dashboard.html
  • docs.html
  • go.mod
    Good: Dependency manifest found (go.mod).
  • index.html
  • input.css
  • news_scraper.go
  • news.html
  • nvd_scraper.go
  • 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.
  • ROADMAP.md
  • start.sh
  • style.css
  • tailwind.config.js
  • validate.go