we-promise/sure
sure
we-promise · Organization · Ruby
The personal finance app for everyone (by everyone)
Snapshot of 2026-09-22 · 721 repos · every number on this page is measured against that date.
Ship status
Still shipping
Last verified push within 30 days.
- Last verified push
- Sep 21, 2026
- Days since that push
- 0 days before this snapshot
- Ship score
- 64 / 100 how it is calculated →
Thresholds: ≤30 days shipping · 31–120 slowed · >120 silent · unreachable for 3 days unverified.
Measured against the snapshot of 2026-09-22, not against today.
How we measure →Repo facts
What the snapshot recorded.
Stars
10K
Snapshot of 2026-09-22
Stars, last 7 weeks
no history yet
History starts 2026-09-22, the first weekly sample after this repo joined the directory.
Forks
510
Snapshot of 2026-09-22
Open issues
571
Issues and pull requests GitHub reports as open
Watchers
39
Accounts subscribed to the repository
License
GNU Affero General Public License v3.0
OSI-approved license. GitHub's own license field, not legal advice.
Created
Jul 23, 2025
Repository creation date on GitHub
Owner
we-promise · Organization
Last verified push Sep 21, 2026
Topics
No GitHub topics are present in the current snapshot.
How it got here
What the classifier decided, and when.
Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 18%, hosted offering 53%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.
Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.97. Answered by jev-1.13.0. How the classification works →
Embed your status
Put this badge on your README.
This is the live badge for we-promise/sure, served from the URL below.[](https://ossean.com/we-promise/sure)
Updates daily. It shows the last verified push — how we measure it.
Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.
Related projects
More in the same current.
discourse
discourse/discourse
A platform for community discussion. Free, open, simple.
chatwoot
chatwoot/chatwoot
Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
gitlabhq
gitlabhq/gitlabhq
GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
forem
forem/forem
For empowering community 🌱
docuseal
docusealco/docuseal
Open source DocuSign alternative. Create, fill, and sign digital documents ✍️
postal
postalserver/postal
📮 A fully featured open source mail delivery platform for incoming & outgoing e-mail