ansible/vscode-ansible

0

/ 100

Documentation78
Engineering91
Health91
TypeScript478MITtoday
Grade a repo

Polished and well engineered. Punching above its star count.

Ansible IDE extension: auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.

Documentation

78

README12pt58

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

91

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/ci.yaml).

Tests18pt95

Test files detected (examples/collections/ansible_collections/my_namespace/my_collection/plugins/modules/my_test.py).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

91

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt93

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 54 / 129
    Commits (30d / 90d)
  • 144
    Forks
  • 61
    Releaseslatest 2y ago

Community

  • 62% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 478
    Watchers

Responsiveness

  • 17h
    Median issue response
  • <1h
    Median PR merge time
  • 121
    Open issues
Repository files69 root entries
  • .claude
  • .config
  • .cursor
  • .devcontainer
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/ci.yaml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • .vscode
  • docs
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • examples
    Good: Test files detected (examples/collections/ansible_collections/my_namespace/my_collection/plugins/modules/my_test.py).
  • images
  • media
  • packages
    Good: Environment pinned via packages/ansible-language-server/.config/Dockerfile.
  • patches
  • scripts
  • src
  • syntaxes
  • test
  • tools
  • webviews
  • .c8rc.json
  • .coderabbit.yaml
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env
    Issue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .issuetracker
  • .markdownlint-cli2.jsonc
  • .markdownlint.yaml
  • .markdownlintignore
  • .mcp.json
  • .npmrc
  • .pre-commit-config.yaml
  • .python-version
  • .readthedocs.yml
  • .vscode-test.mjs
  • .vscodeignore
  • .yamllint
  • AGENTS.md
  • ansible-language-configuration.json
  • biome.json
  • CHANGELOG.md
  • codecov.yml
  • commitlint.config.js
  • Containerfile
  • cspell.config.yaml
  • eslint.config.mjs
  • jinja-language-configuration.json
  • knip.ts
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • package.nls.json
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • pyproject.toml
  • README.md
    Good: README is present.
    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.
    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.
    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.
  • renovate.json
  • settings.toml
  • sonar-project.properties
  • Taskfile.base.yml
  • Taskfile.yml
  • tsconfig.base.json
  • tsconfig.json
  • tsdoc.json
  • uv.lock
  • vite.config.mts
  • vitest.config.ts
  • wdio.conf.ts
  • zensical.toml