layumi/layumi.github.io

0

/ 100

Documentation73
Engineering20
Health91
HTML6MIT1d ago
Grade a repo

Early stage. Tests, CI, and a strong README would raise this score quickly.

Zhedong Zheng Homepage https://www.zdzheng.xyz

Documentation

73

README12pt55

README is present.

Contributing guide5pt55

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

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

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

20

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

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.

CI/CD14pt40

CI is configured (.github/workflows/google_scholar_crawler.yaml).

Reproducibility6pt70

Lockfile present (google_scholar_crawler/requirements.txt). Installs are reproducible.

Project health

91

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt90

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 3
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 217d 4h
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files66 root entries
  • _authors
  • _data
  • _drafts
  • _includes
  • _layouts
  • _pages
  • _plugins
  • _portfolio
  • _posts
  • _publications
  • _sass
  • _tag
  • _talks
  • _teaching
  • .github
    Good: CI is configured (.github/workflows/google_scholar_crawler.yaml).
  • assets
  • awards
  • Awesome-Geolocalization
  • Awesome-reID
  • coauthors
  • files
  • google_scholar_crawler
    Good: Lockfile present (google_scholar_crawler/requirements.txt). Installs are reproducible.
  • images
  • markdown_generator
  • old-homepage
  • rawblog
  • resource-img
  • scripts
  • talkmap
  • _config.dev.yml
  • _config.yml
  • .DS_Store
    Issue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .htaccess
  • ACMMM2023Workshop
  • ACMMM2024Workshop-UAV
  • ACMMM2025Workshop-UAV
  • ACMMM2026Workshop-UAV
  • Awesome-Aerial-Spatial-Intelligence
  • baidu_verify_QICyQDG3I2.html
  • CHANGELOG.md
  • CNAME
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • dfd88821f5124a23883543e712b1d8ad.txt
  • DG-Net
  • favicon.ico
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • ICME2022SS
  • LICENSE
    Good: Licensed under MIT.
  • MORE2024
  • MORE2025
  • package-old.json
  • package.json
  • poster_page
  • Pytorch-ReID
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • robots.txt
  • sitemap-bak.xml
  • synthir26
  • talkmap.ipynb
  • talkmap.py
  • update_leaderboard.py
  • vercel.json
  • yandex_aaaf4c661ebb1ed7.html
  • zhedong-resume.pdf