nestjs/mongoose

0

/ 100

Documentation80
Engineering74
Health95
TypeScript568MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Mongoose module for Nest framework (node.js) 🍸

Documentation

80

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

74

Tests18pt35

Test files detected (tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.circleci/config.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

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)
  • 115
    Forks
  • 43
    Releaseslatest 5y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 568
    Watchers

Responsiveness

  • 3d 17h
    Median issue response
  • 4d 18h
    Median PR merge time
  • 4
    Open issues
Repository files22 root entries
  • .circleci
    Good: CI is configured (.circleci/config.yml).
  • .github
    Good: Issue or PR templates present.
  • .husky
  • lib
  • tests
    Good: Test files detected (tests).
  • .commitlintrc.json
  • .gitignore
    Good: .gitignore present.
  • .npmignore
  • .nvmrc
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • .release-it.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • LICENSE
    Good: Licensed under MIT.
  • oxlint.json
  • 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.
  • renovate.json
  • tsconfig.build.json
  • tsconfig.json
  • vitest.config.ts