stdlib-js/stats
Grade a repo

0

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Standard library statistical functions.

Documentation78
Engineering71
Health100
JavaScript10Apache-2.0today

Documentation

78

Contributing guide5pt52

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

71

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt68

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

Tests18pt80

Test files detected (anova1/test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 10
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files85 root entries
  • .github
    Good: CI is configured (.github/workflows/test_bundles.yml).
    Good: Issue or PR templates present.
  • anova1
    Good: Test files detected (anova1/test).
  • array
  • bartlett-test
  • base
  • binomial-test
  • chi2gof
  • chi2test
  • cumax
  • cumin
  • docs
  • examples
  • fligner-test
  • incr
  • iter
  • kde2d
  • kruskal-test
  • kstest
  • levene-test
  • lib
  • lowess
  • max
  • max-by
  • maxabs
  • maxsorted
  • mean
  • meankbn
  • meankbn2
  • meanors
  • meanpn
  • meanpw
  • meanwd
  • mediansorted
  • midrange
  • midrange-by
  • min
  • min-by
  • minabs
  • minsorted
  • nanmax
  • nanmax-by
  • nanmaxabs
  • nanmean
  • nanmeanors
  • nanmeanpn
  • nanmeanwd
  • nanmidrange
  • nanmidrange-by
  • nanmin
  • nanmin-by
  • nanminabs
  • nanrange
  • nanrange-by
  • padjust
  • pcorrtest
  • range
  • range-by
  • rangeabs
  • ranks
  • strided
  • test
  • ttest
  • ttest2
  • vartest
  • wilcoxon
  • ztest
  • ztest2
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintrc.js
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmignore
  • .npmrc
  • branches.md
  • CHANGELOG.md
  • CITATION.cff
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • CONTRIBUTORS
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • NOTICE
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README has code examples.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.