cognizant-ai-lab/neuro-san

0

/ 100

Documentation86
Engineering78
Health100
Python121Apache-2.0today
Grade a repo

Polished and well engineered. Punching above its star count.

Neuro AI System of Agent Networks

Documentation

86

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

78

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.

Tests18pt80

Test files detected (neuro_san/test).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.flake8).

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

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)
  • 42
    Forks
  • 172
    Releaseslatest 1y ago

Community

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

Responsiveness

  • 5d 20h
    Median issue response
  • 2h
    Median PR merge time
  • 102
    Open issues
Repository files23 root entries
  • .github
    Good: CI is configured (.github/workflows/checkmarx.yml).
  • build_scripts
  • docs
  • neuro_san
    Good: Test files detected (neuro_san/test).
    Good: Environment pinned via neuro_san/deploy/Dockerfile.
  • quick-start
  • tests
  • .coveragerc
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitignore
    Good: .gitignore present.
  • .pylintrc
  • .pymarkdownlint.yaml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • MANIFEST.in
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pytest.ini
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-build.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • SECURITY.md
    Good: Security policy present.
  • setup.py
  • SUPPORT.md