layer5io/docs
Grade a repo

86

/ 100

GradeB

Well engineered for its size. A portfolio piece worth showing off.

Top 20% of 5,156 graded repos

Documentation and Developer resources for Layer5 products

Documentation91
Engineering79
Health97
JavaScript91Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

91

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/build-and-preview-docs.yml).

Tests18pt80

A test script is configured in package.json.

Reproducibility6pt85

Lockfile present (go.sum). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt92

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

Community

  • 100% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 91
    Watchers

Responsiveness

  • 14h
    Median issue response
  • <1h
    Median PR merge time
  • 85
    Open issues
Repository files34 root entries
  • .github
    Good: CI is configured (.github/workflows/build-and-preview-docs.yml).
    Good: Issue or PR templates present.
  • archive
  • assets
  • build
  • charts
  • content
  • data
  • docs
  • i18n
  • layouts
  • proposals
  • static
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • build-digest.py
  • CNAME
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • compose.yaml
  • config.yaml
  • CONTRIBUTING-gitflow.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • hugo.toml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • package-lock.json
  • package.json
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/layer5io/docs)](https://www.repo-grade.com/report/layer5io/docs)

More graded JavaScript repos