creatornader/atrib
Grade a repo

0

/ 100

GradeA

Polished work that hasn't found its audience yet.

Verifiable agent actions. A verifiable action layer for agents: control what runs, coordinate what carries forward, and prove what happened.

Documentation85
Engineering92
Health97
TypeScript6Apache-2.0today

Documentation

85

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

92

CI/CD14pt72

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

Tests18pt100

Test files detected (apps/dashboard/test).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt92

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)
  • 0
    Forks
  • 439
    Releaseslatest 1mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 6
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files47 root entries
  • .changeset
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 4 ecosystems (github-actions, npm, cargo, pre-commit). Dependencies stay current.
    Good: Issue or PR templates present.
  • apps
    Good: Test files detected (apps/dashboard/test).
  • docs
  • metrics
  • packages
    Good: Environment pinned via packages/integration/examples/browserbase-stagehand/live-demo/Dockerfile.
  • patches
  • policies
  • proof-packets
  • scripts
  • services
  • skills
  • spec
  • _typos.toml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .nvmrc
  • .oss-twin.yaml
  • .pre-commit-config.yaml
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • ARCHITECTURE.md
  • atrib-spec.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • DECISIONS.md
  • DESIGN.md
  • DOC-SYNC-TRIGGERS.md
  • eslint.config.js
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LOOP.md
  • METRICS.md
  • NOTICE
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • PRIOR-ART.md
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • textleaks.yaml
  • tsconfig.base.json
  • turbo.json
  • vitest.config.ts