openxlings/xlings

0

/ 100

Documentation89
Engineering58
Health68
C++586Apache-2.01d ago
Grade a repo

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

Universal package infrastructure with OS-like SubOS isolation - Multi-version · Rootless · Decentralized Index · Agent-ready.

Documentation

89

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

58

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/xlings-ci-aarch64.yml).

Tests18pt80

Test files detected (docs/spec).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 47
    Forks
  • 63
    Releaseslatest 2mo ago

Community

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

Responsiveness

  • 22h
    Median issue response
  • <1h
    Median PR merge time
  • 23
    Open issues
Repository files21 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/xlings-ci-aarch64.yml).
    Good: Issue or PR templates present.
  • config
  • docs
    Good: Test files detected (docs/spec).
  • examples
  • src
    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.
  • tests
  • tools
  • xmake
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .xlings.json
  • AGENTS.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mcpp.lock
  • mcpp.toml
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.zh.md
  • skills-lock.json
  • xmake.lua