portwood-global-solutions/docgen

0

/ 100

Documentation75
Engineering47
Health94
Apex85Apache-2.01d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Free, native document generation for Salesforce. PDF, DOCX, XLSX, PPTX — merge tags, images, barcodes, QR codes, bulk generation, Flow actions. 100% Apex + LWC, zero external dependencies.

Documentation

75

Install and run instructions9pt45

README documents how to install the project.

README12pt80

README is present.

Contributing guide5pt89

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

47

Tests18pt0

No tests detected anywhere in the repository.

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

CI/CD14pt57

CI is configured (.github/workflows/format-check.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Dependency manifest6pt82

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)
  • 23
    Forks
  • 112
    Releaseslatest 2mo ago

Community

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

Responsiveness

  • 9h
    Median issue response
  • <1h
    Median PR merge time
  • 4
    Open issues
Repository files33 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/format-check.yml).
    Good: Issue or PR templates present.
  • .husky
  • .tmp
  • .vscode
  • assets
  • config
  • DEMO TEMPLATES
  • demos
  • docs
  • force-app
  • manifest
  • scripts
  • .forceignore
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • code-analyzer.yml
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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.
  • CONTRIBUTORS.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.
  • sfdx-project.json
  • THIRD-PARTY-NOTICES.md
  • TRIAGE.md
  • UserGuide.md