Aware: The Free Mental Health App With Open-Source Code

Most free mental health apps ask you to trust a privacy policy and a "science-based" badge, and that's the end of the audit trail. Aware, built by the Swedish nonprofit foundation 29k, hands over something most competitors don't: the actual source code. The README states the pitch directly — "Aware is a free app for mental health, wellbeing and inner development brought to you by the non-profit foundation 29k" — and then, unlike a marketing page, backs it with a public, AGPL-3.0-licensed repository anyone can read line by line.

That's the claim worth testing rather than taking on faith: is this a real, maintained open-source project, or a nonprofit's one-time code dump that nobody touches anymore? The 29ki/29k repository itself — commit history, license files, dependency lists — is where that gets checked.

What this free, open-source mental health app actually is, in its own words

The README is explicit about lineage: "This is the 2.0 open-source version based on the learnings from the previous 29k: Mental Health App." In other words, Aware isn't 29k's first attempt — it's a rebuild, with the source itself made public the second time around. The README links out to the app on the iOS App Store and Google Play rather than hosting the app anywhere on GitHub; the repository is the code, not the distribution channel.

The 29ki organization profile states the group's mission directly: "29 000 days in a lifetime. Make them count". It lists Stockholm, Sweden as its base, 12 followers, and 26 public repositories — the 29k repo itself is the only one pinned, described there as "the repository of the free, non-profit, open-source and co-created mental health app Aware."

The license split — and a badge that doesn't match it

Here's the first thing worth checking rather than skimming past: the README's own License section states two different terms for two different parts of the project. "The computer software is licensed under the AGPL-3.0 license," it says, while "the content in the /content directory including its subdirectories are licensed under the CC-BY-SA-4.0 license" — a deliberate split between the app's code (copyleft, so anyone who runs a modified public version has to share their changes back) and its guided-session content (a Creative Commons share-alike license, more common for text and media than software).

Except the README's own license badge near the top says something else entirely: its alt text reads "29k is released under the Creative Commons Zero v1.0 Universal" — CC0, a public-domain dedication that waives all rights, not the AGPL-3.0 the License section actually names. The raw LICENSE file in the repo settles which one actually governs the code: it's the GNU Affero General Public License, opening with "GNU AFFERO GENERAL PUBLIC LICENSE, Version 3, 19 November 2007" — confirming the License section's prose, not the badge. It's a small inconsistency, but a telling one: even a project built around transparency can leave a stale badge pointing at the wrong license for anyone who doesn't click through.

What it's actually built with

Aware is a monorepo, and the repository's top-level file tree lays out the pieces: a client directory for the mobile app, functions for backend logic, cms for content tooling, content for the licensed session material itself, and a web directory alongside bigQuery/schemaViews.

The client's package.json names the app 29k-cupcake-client and pins react-native at version 0.74.3, alongside @react-navigation/native, @react-native-firebase/auth, and the state-management library zustand. It also lists a dependency on @stripe/stripe-react-native — a real line in the dependency list, not a guess, but what it's actually wired up to isn't documented anywhere in the parts of the repo checked for this piece.

The client folder itself confirms the React Native build setup directly: ios and android platform folders, fastlane for deployment, and metro.config.js. The separate cms directory is its own TypeScript project, built with Vite and tested with Jest — tooling for managing the guided-session content, kept apart from the client app's codebase.

Still maintained — at nonprofit pace, not startup pace

A public repo proves nothing on its own if nobody's touched it in years. The commit history on main shows its most recent commits dated September 10, 2026 — about five weeks before this piece was checked — a small batch adding a new services-sponsorship credit and fixing an unrelated typo (a link pointing to "Daily.com" corrected to "Daily.co"). Before that, the trail thins out: merged pull requests show activity on June 2, April 18, and January 7 of 2026. That's a repository that's genuinely still alive, just moving in nonprofit-sized bursts rather than daily commits — a different rhythm than the venture-backed or solo-hacker projects this blog usually checks, and worth naming plainly rather than papering over.

The backlog tells a similar story: the pull requests tab reports 68 open PRs against a comparatively small set of recent merges, and the releases page shows no tagged releases at all — the app ships to app stores, evidently, but not through GitHub's release mechanism. For a side project that's a yellow flag; for a nonprofit running a monorepo with a small, mostly volunteer team, it reads more like an open backlog than an abandoned one.

Who's actually building it

The project credits its contributors using the all-contributors convention, and the raw .all-contributorsrc file lists 59 separate entries — code, design, content, research, and project-management roles, per the README's own description of that table. That's a meaningfully larger circle than a two-person nonprofit side project, even if the commit cadence above shows it isn't a full-time engineering team either.

Where this piece's checking runs out

A few things are worth being direct about rather than filling in from memory.

First: the app stores themselves — Apple's App Store and Google Play — were unreachable during this session's fact-checking. Nothing here about ratings, install counts, or the exact in-store description can be stated as verified; the only confirmed app-store detail is that the README links to both.

Second: nothing in the parts of the repository reachable this session documents what the bundled Stripe SDK is actually used for inside the app. It's listed as a real dependency, not a guess, but its purpose — donations, a paid tier, something else — isn't something this piece can confirm.

Third, and most important for a mental health app specifically: this piece did not find a peer-reviewed study or published clinical trial backing Aware's content during this research. That absence doesn't mean one doesn't exist, only that it couldn't be confirmed here — and it's a meaningfully different claim than "AGPL-licensed, 59 contributors, active commits," all of which were checked directly against the repository.

This isn't a crisis resource. Nothing in the repository frames it as one, and if you need immediate mental health support, a guided-meditation app — open-source or not — isn't the right tool; a crisis line or a licensed professional is.

What this generalizes to

The useful habit here isn't specific to mental health apps: before trusting a "free," "nonprofit," or "science-based" badge on any app that touches something as personal as your mental health or your money, check whether the claim is backed by something inspectable — the same discipline this blog has applied to whether a donation platform's transparency promise is backed by a public ledger or just a tagline, whether a nutrition grading formula is a readable module or a black box, or whether a spaced-repetition algorithm is published code rather than a trade secret.

Aware passes that check further than most: its code is genuinely AGPL-licensed, its license badge is simply wrong rather than its license being fake, and its commit log shows real, if unhurried, maintenance. What it doesn't pass — because almost nothing in this space does without being asked directly — is "science-based" as a verifiable claim rather than a marketing line. That gap is worth remembering the next time any wellness app puts a research-sounding word next to its name.