keithrozario/klayers

0

/ 100

Documentation78
Engineering68
Health100
Python2,492Other1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Python Packages as AWS Lambda Layers

Documentation

78

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt60

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.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

68

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

Tests18pt80

Test files detected (pipeline/Serverless/common/tests).

Reproducibility6pt80

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pipeline/Serverless/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)
  • 353
    Forks
  • 8
    Releaseslatest 3mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,492
    Watchers

Responsiveness

  • 4h
    Median issue response
  • —
    Median PR merge time
  • 2
    Open issues
Repository files9 root entries
  • .github
    Good: CI is configured (.github/workflows/container_builds.yml).
    Good: Issue or PR templates present.
  • deployments
  • documentation
  • pipeline
    Good: Test files detected (pipeline/Serverless/common/tests).
    Good: Lockfile present (pipeline/Serverless/package-lock.json). Installs are reproducible.
    Good: Environment pinned via pipeline/container_images/build_images/p312_arm64/Dockerfile.
    Good: Dependency manifest found (pipeline/Serverless/package.json).
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • LICENSE
    Good: Licensed under Other.
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.