Getting noticed, but rough fundamentals could turn visitors away.

API pública para diferentes datos de Argentina

Documentation

53

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.

README12pt85

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

License6pt100

Licensed under MIT.

Engineering

25

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

CI/CD14pt40

CI is configured (.github/workflows/fci-fondos.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (apps/cafci-worker/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files12 root entries
  • .github
    Good: CI is configured (.github/workflows/fci-fondos.yml).
    Good: Issue or PR templates present.
  • .vscode
  • api
  • apps
    Good: Environment pinned via apps/cafci-worker/Dockerfile.
    Good: Dependency manifest found (apps/cafci-worker/package.json).
  • datos
  • .env.template
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • .prettierignore
  • CNAME
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.