Strong community interest, but tests, CI, or docs need work.
A Proof-oriented Programming Language
Documentation
75
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
42
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.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/build-all.yml).
Test files detected (.scripts/fstardoc/tests).
Project health
100
Dependency manifest found (examples/algorithms/algorithms.sln).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 256Forks
- 90Releaseslatest 9y ago
Community
- —Community health
- —authors own >50% of commits
- 3,047Watchers
Responsiveness
- 1hMedian issue response
- 9hMedian PR merge time
- 561Open issues
Repository files42 root entries
- .ci
- .completion
- .copilotGood: .gitignore present.
- .devcontainer
- .dockerGood: Environment pinned via .docker/base/Dockerfile.
- .githubGood: CI is configured (.github/workflows/build-all.yml).
- .hooks
- .nix
- .scriptsGood: Test files detected (.scripts/fstardoc/tests).
- .vscode
- bare-tests
- contrib
- doc
- examplesGood: Dependency manifest found (examples/algorithms/algorithms.sln).
- fsharp
- mk
- pulse
- src
- stage0
- stage1
- stage2
- stage3
- tests
- ulib
- .gitattributes
- .gitignore
- .gitmodules
- .ignore
- .merlin
- CHANGES.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- flake.lock
- flake.nix
- FStar.fst.config.json
- fstar.opam
- INSTALL.md
- karamel
- LICENSEGood: Licensed under Apache-2.0.
- LICENSE-fsharp.txt
- Makefile
- README.mdGood: 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.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.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.
- version.txt