piercefreeman / waymark
🧭 Distributed background workflows, durably executed
- Stars
- 158 stars
- Forks
- 6 forks
- Language
- Rust
- License
- MIT
- Created
- Nov 16, 2025
- Last push
- Nov 11, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- Durable execution from the readme:
waymark is a library to let you build durable background tasks that withstand server restarts, task crashes, and long-running jobs.
- Workflow engine from the readme:
**Workflows** are the control flow: loops, conditionals, parallel branches. They orchestrate actions but don't do heavy lifting themselves.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 8, 2026: +112 stars in 7 days.
Star History
185 days recorded, May 11, 2026 – Nov 11, 2026 (UTC). Net change +154 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/piercefreeman/waymark) Badge
[](https://awesomerepos.com/piercefreeman/waymark) Timeline
It gained stars on 13 of the 185 days recorded since May 11, 2026.
Its largest 7 days were Nov 5, 2026 to Nov 11, 2026: 148 stars.
In the 30 days to Nov 11, 2026 it got 149 stars, 14800% more than in the 30 days before.
- Created on the Repository Host
- Release v0.30.dev7
- Release v0.30.dev8
- Release v0.30.dev14
- Release v0.30.0
- Largest star day recorded: +76 stars, the same day as release v0.30.1
- Release v0.30.1
- Reached 100 stars, 356 days after it was created
- +36 stars in one day
- Entered the Repository Index: +112 stars in 7 days
- +15 stars in one day
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 4 Observations, Nov 9, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 2 of 3 days.
- Nov 10, 2026: new push
- Nov 11, 2026: no new push
- Nov 12, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 10, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 3 tasks for the maintainers of piercefreeman/waymark.
Improve the Health Facts of the GitHub repository piercefreeman/waymark. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/piercefreeman/waymark. A change to the repository can improve each of the 3 items below. Each item gives the measured fact or score, and a task. 1. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-10). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 2. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-10). Rule: GitHub finds a security policy (SECURITY.md in the repository or in the owner's .github repository). Task: Add SECURITY.md at the root or in .github/. Say which versions get security fixes and how to report a vulnerability privately. If GitHub private vulnerability reporting is on, point to it. Ask me for the contact; do not invent one. 3. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-10). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
4 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-11, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
867 commits on the default branch in the last 13 weeks (GitHub, 2026-11-10). Source
-
Yes: Commits in 26 or more of the last 52 weeks
Commits in 52 of the last 52 weeks (GitHub, 2026-11-10). Source
- 20
- 106
- 47
- 46
- 13
- 30
- 4
- 6
- 7
- 15
- 17
- 15
- 11
- 3
- 16
- 41
- 49
- 83
- 60
- 63
- 56
- 55
- 25
- 18
- 15
- 15
- 44
- 41
- 5
- 18
- 12
- 28
- 14
- 12
- 32
- 43
- 52
- 47
- 38
- 42
- 55
- 42
- 52
- 42
- 57
- 42
- 189
- 59
- 86
- 14
- 52
- 135
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v0.30.1 on 2026-11-06, 5 days ago. 10 or more releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v0.30.1. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-10).
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-10).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 10, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 12, 2026: 158 stars, 6 forks, last push Nov 11, 2026, not archived. One of 4 Observations since Nov 9, 2026.