Solid engineering. The main gap is visibility.

A jest extension to deal with screenshots and all sorts of images.

Documentation

85

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

84

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (yarn.lock). Installs are reproducible.

Tests18pt100

Test files detected (example/__tests__).

CI/CD14pt100

CI is configured (.travis.yml).

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

Project health

62

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt93

Dependency manifest found (package.json).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • Median issue response
  • Median PR merge time
  • 0
    Open issues
Repository files20 root entries
  • benchmark
  • example
    Good: Test files detected (example/__tests__).
  • images
  • src
  • typings
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
    Good: CI is configured (.travis.yml).
  • index.d.ts
  • jest-framework-setup.ts
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • 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.
    Good: README documents how to run the project.
  • reporter.js
  • tsconfig-production.json
  • tsconfig-webpack.json
  • tsconfig.json
  • tslint.json
  • webpack.config.js
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.