iamcorey/coreychiu-portfolio-template

0

/ 100

Documentation68
Engineering30
Health89
TypeScript459MIT1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

portfolio template by corey chiu

Documentation

68

Contributing guide5pt0

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.

Install and run instructions9pt55

README documents how to install the project.

README12pt90

README is present.

License6pt100

Licensed under MIT.

Engineering

30

Tests18pt0

No tests detected anywhere in the repository.

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

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/main.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Project health

89

Dependency manifest6pt65

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)
  • 72
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 16h
    Median issue response
  • 1d 14h
    Median PR merge time
  • 2
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/main.yml).
  • public
  • src
  • .env.example
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • components.json
  • LICENSE
    Good: Licensed under MIT.
  • mdx-components.tsx
  • next-env.d.ts
  • next.config.mjs
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
  • postcss.config.js
  • prettier.config.js
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.zh.md
  • tailwind.config.ts
  • tsconfig.json
  • typography.ts