csstools/postcss-plugins
Grade a repo

93

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 8% of 5,156 graded repos

PostCSS Tools and Plugins

Documentation84
Engineering100
Health89
CSS1,049MIT-01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 to address
  1. 1
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

  4. 4
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

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

84

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT-0.

Engineering

100

Tests18pt100

Test files detected (cli/csstools-cli/test).

CI/CD14pt100

CI is configured (.github/workflows/lint.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

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

  • 92 / 208
    Commits (30d / 90d)
  • 85
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,049
    Watchers

Responsiveness

  • 209d 16h
    Median issue response
  • 14h
    Median PR merge time
  • 12
    Open issues
Repository files32 root entries
  • .github
    Good: Licensed under MIT-0.
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Dependabot covers 3 ecosystems (npm, npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • cli
    Good: Test files detected (cli/csstools-cli/test).
  • e2e
  • e2e-package-managers
  • experimental
  • packages
  • plugin-packs
  • plugins
  • plugins-stylelint
  • postcss-recipes
  • rollup
  • sites
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .stylelintignore
  • api-extractor.json
  • AUTHORING_GUIDELINES.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • eslint.config.mjs
  • knip.json
  • LICENSE.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (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.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    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.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json
  • UPDATING_POSTCSS.md
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/csstools/postcss-plugins)](https://www.repo-grade.com/report/csstools/postcss-plugins)

More graded CSS repos