chainguard-images/images

0

/ 100

Documentation70
Engineering40
Health100
HCL678Apache-2.01d ago
Grade a repo

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

Public Chainguard Images

Documentation

70

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

40

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 config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

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

Reproducibility6pt92

Lockfile present (images/node/example/package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (images/node/example/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)
  • 174
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 20h
    Median issue response
  • <1h
    Median PR merge time
  • 112
    Open issues
Repository files19 root entries
  • .chainguard
  • .github
    Good: CI is configured (.github/workflows/actionlint.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • images
    Good: Lockfile present (images/node/example/package-lock.json). Installs are reproducible.
    Good: Environment pinned via images/node/example/Dockerfile.
    Good: Dependency manifest found (images/node/example/package.json).
  • tflib
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .terraform.lock.hcl
  • .yam.yaml
  • BEST_PRACTICES.md
  • BUILDING.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • main.tf
  • Makefile
  • 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.
    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.
    Good: README documents how to run the project.
  • reinstated-images.txt
  • SECURITY.md
    Good: Security policy present.
  • WITHDRAWING_IMAGES.md
  • withdrawn-images.txt
  • withdrawn-repos.txt