opencraft-app / opencraft
TypeScript agent workbench for Web, Electron and Expo with pluggable execution hosts and managed Web updates
- Stars
- 191 stars
- Forks
- 1 forks
- Language
- TypeScript
- License
- MIT-0
- Created
- Oct 27, 2026
- Last push
- Nov 12, 2026
- Updated
- Nov 13, 2026
Why these Tags: an agent read the README and quoted it
- Coding agent manager from the readme:
恢复已支持的原生历史、保留草稿、查看工具活动与已上报的 Token 用量，在一个工作台里发送任务或停止执行。
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 11, 2026: +101 stars in 7 days.
Star History
9 days recorded, Nov 4, 2026 – Nov 12, 2026 (UTC). Net change +197 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/opencraft-app/opencraft) Badge
[](https://awesomerepos.com/opencraft-app/opencraft) Timeline
It gained stars on 4 of the 9 days recorded since Nov 4, 2026.
- Created on the Repository Host
- Reached 100 stars, 14 days after it was created
- Largest star day recorded: +104 stars
- Entered the Repository Index: +101 stars in 7 days
- +42 stars in one day
- +49 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 2 Observations, Nov 12, 2026 – Nov 13, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 13, 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 13, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of opencraft-app/opencraft.
Improve the Health Facts of the GitHub repository opencraft-app/opencraft. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/opencraft-app/opencraft. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-13). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-13). 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
3 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-12, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
620 commits on the default branch in the last 13 weeks (GitHub, 2026-11-13). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 3 of the last 52 weeks (GitHub, 2026-11-13). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 266
- 218
- 136
Releases
1 of 3 checks (1 without data)Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-13). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksObservations
Latest Observation, Nov 13, 2026: 191 stars, 1 fork, last push Nov 12, 2026, not archived. One of 2 Observations since Nov 12, 2026.