facelessuser/pymdown-extensions

0

/ 100

Documentation61
Engineering71
Health95
Python1,123Other1d ago
Grade a repo

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

Extensions for Python Markdown

Documentation

61

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt48

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

Licensed under Other.

Engineering

71

Tests18pt35

Test files detected (tests).

CI/CD14pt85

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

Reproducibility6pt90

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Dependency manifest6pt85

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)
  • 270
    Forks
  • 117
    Releaseslatest 9y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,123
    Watchers

Responsiveness

  • 5h
    Median issue response
  • <1h
    Median PR merge time
  • 19
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 2 ecosystems (npm, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • docs
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • pymdownx
  • requirements
  • tests
    Good: Test files detected (tests).
  • tools
  • .babelrc
  • .codecov.yml
  • .coveragerc
  • .eslintrc
    Good: Linter or formatter configured (.eslintrc).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .pyspelling.yml
  • .stylelintrc
  • gulpfile.babel.mjs
  • hatch_build.py
  • LICENSE.md
    Good: Licensed under Other.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pyproject.toml
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
    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.
    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.
  • run_tests.py
  • SECURITY.md
    Good: Security policy present.
  • zensical.yml