UCS-Care-Group / mailcraft
MailCraft: an open-source, clean-room mail, calendar and contacts program in pure Rust, for Microsoft 365, Outlook.com and IMAP. Early alpha.
- Stars
- 542 stars
- Forks
- 100 forks
- Language
- Rust
- License
- APACHE-2.0
- Created
- Oct 12, 2026
- Last push
- Nov 13, 2026
- Updated
- Nov 12, 2026
Why these Tags: an agent read the README and quoted it
- Calendar from the readme:
**Calendar:** day, work-week, week and month views; appointments and meetings with attendees; recurrence
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: +132 stars in 7 days.
Star History
30 days recorded, Oct 14, 2026 – Nov 12, 2026 (UTC). Net change +579 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/UCS-Care-Group/mailcraft) Badge
[](https://awesomerepos.com/UCS-Care-Group/mailcraft) Timeline
It gained stars on each of the 30 days recorded since Oct 14, 2026.
Its largest 7 days were Nov 6, 2026 to Nov 12, 2026: 370 stars.
- Created on the Repository Host
- Reached 100 stars, 14 days after it was created
- Release v0.9.0
- Release v0.10.0
- Release v0.11.0
- Release v0.11.1
- Largest star day recorded: +134 stars, 2 days after release v0.11.1
- Entered the Repository Index: +132 stars in 7 days
- +109 stars in one day
- Reached 500 stars, 31 days after it was created
- +101 stars in one day
- Release v0.12.0
- 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 +22. 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 1 task for the maintainers of UCS-Care-Group/mailcraft.
Improve the Health Facts of the GitHub repository UCS-Care-Group/mailcraft. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/UCS-Care-Group/mailcraft. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. The Scorecard result is from 2026-11-13: https://scorecard.dev/viewer/?uri=github.com/UCS-Care-Group/mailcraft 1. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-13). 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. 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-13, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
1958 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 5 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
- 166
- 446
- 268
- 613
- 465
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v0.12.0 on 2026-11-12, 1 day 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.12.0. Source
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-13).
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-13). Source
OpenSSF Scorecard: 18 checks on Nov 13, 2026
Each check has its own score, from 0 to 10. AwesomeRepos does not show the Scorecard aggregate score, and these checks are not in the count above. Source
- Binary-Artifacts
- 10 of 10
- Branch-Protection
- 3 of 10
- CI-Tests
- 10 of 10
- CII-Best-Practices
- 7 of 10
- Code-Review
- 6 of 10
- Contributors
- 10 of 10
- Dangerous-Workflow
- 10 of 10
- Dependency-Update-Tool
- 10 of 10
- Fuzzing
- 10 of 10
- License
- 10 of 10
- Maintained
- 0 of 10
- Packaging
- No result
- Pinned-Dependencies
- 10 of 10
- SAST
- 10 of 10
- Security-Policy
- 10 of 10
- Signed-Releases
- 10 of 10
- Token-Permissions
- 10 of 10
- Vulnerabilities
- 7 of 10
Community files
3 of 3 checksObservations
Latest Observation, Nov 13, 2026: 542 stars, 100 forks, last push Nov 13, 2026, not archived. One of 2 Observations since Nov 12, 2026.