akiver/cs-demo-manager

0

/ 100

Documentation43
Engineering85
Health100
TypeScript1,926MIT1d ago
Grade a repo

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

Companion application for your Counter-Strike demos.

Documentation

43

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt10

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

→ Add a section showing how to install dependencies.

README12pt58

README is present.

License6pt100

Licensed under MIT.

Engineering

85

CI/CD14pt57

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

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (src/common/video/sequences/build-players-event-sequences.test.ts).

Linting and formatting5pt100

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

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)
  • 235
    Forks
  • 95
    Releaseslatest 10y ago

Community

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

Responsiveness

  • 18d 13h
    Median issue response
  • 10d 20h
    Median PR merge time
  • 32
    Open issues
Repository files35 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build_cs_plugins.yml).
    Good: Issue or PR templates present.
  • .vite-hooks
  • .vscode
  • build-assets
  • cs2-server-plugin
  • csgo-server-plugin
  • docker
    Good: Environment pinned via docker/docker-compose.yml.
  • linter
  • scripts
  • skills
  • src
    Good: Test files detected (src/common/video/sequences/build-players-event-sequences.test.ts).
  • static
  • types
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .node-version
  • AGENTS.md
  • CLAUDE.md
  • crowdin.yml
  • electron-builder.config.mjs
  • knip.ts
  • LICENSE
    Good: Licensed under MIT.
  • lingui.config.ts
  • lint-plugin.js
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • postcss.config.mjs
  • preview.png
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.json
  • vite.config.ts