getaura 0.1.10 → 0.3.0

package/LICENSE

@@ -0,0 +1,126 @@
+# License
+
+Copyright 2026 John Fazio
+
+Parts of this package are licensed differently:
+
+- **What Aura writes into your project** is yours. The files in `templates/` and `plugin/`, and any file or
+  text Aura generates for your repository (skills, agent rules, commands, workflows, configs, guides, docs),
+  are licensed under the MIT No Attribution license (MIT-0) in `templates/LICENSE`. You can use, change and
+  share your copies without restriction or attribution.
+- **Third-party code** bundled into `dist/` keeps its own license; see `THIRD-PARTY-NOTICES.md`.
+- **Everything else** in this package is licensed under the Functional Source License, Version 1.1,
+  MIT Future License, below.
+
+---
+
+# Functional Source License, Version 1.1, MIT Future License
+
+## Abbreviation
+
+FSL-1.1-MIT
+
+## Notice
+
+Copyright 2026 John Fazio
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the MIT license that is effective on the second anniversary of the date we make
+the Software available. On or after that date, you may use the Software under
+the MIT license, in which case the following will apply:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -18,18 +18,20 @@ Your agent runs the setup and sends you a link to connect your pilot key in the
 npx getaura init
 ```
 
-`init` checks git and the GitHub CLI, asks which coding agent you use, opens your browser to connect your pilot key, drafts your product brief, installs the Aura skill, offers to install the `aura` command and runs your first scan. After that, run `aura scan` from any folder.
+`init` checks git and the GitHub CLI, asks which coding agent you use, opens your browser to connect your pilot key, drafts your product brief, installs the Aura skill, stops Claude Code from opening your `.env` files, offers to install the `aura` command and runs your first scan. After that, run `aura check` from any folder. Every Aura command needs your pilot key; on a new computer, `aura login` connects it.
 
-To install the `aura` command yourself: `npm install -g getaura`. Without it, use `npx getaura <command>` (for example `npx getaura scan`).
+To install the `aura` command yourself: `npm install -g getaura`. Without it, use `npx getaura <command>` (for example `npx getaura check`).
 
 ## What you get
 
 - **An Aura score** from deterministic checks across security, agent setup, foundations and structure, explained in plain language.
+- **Aura knows what you're building.** It works out whether each project in the repo is a web app, website, API, mobile app, CLI, library or extension, and which tools it uses, and shows this under the score. `aura inventory` shows why it thinks so. If it guessed wrong, say so during `aura init` or run `aura config kind <kind>` (in a monorepo, add the folder: `aura config kind web-app apps/web`). The correction is saved in `.aura/config.json`, so commit it.
+- **Your setup**: what each project has in place (database, sign-in, email, error monitoring, rate limiting, tests, CI…) and what a project like it usually needs but is missing, in `aura inventory` and the report. It's advice only and never changes the score, and any tool that does the job counts.
 - **Next steps** in priority order. After a scan (or with `aura next`), tick the ones you want in the terminal and Aura does them.
 - **Fixes as pull requests you approve**: `aura apply foundation` puts your brief, agent rules, skills, CI and env example in place in one PR, and `aura fix <finding>` has Aura's agent make code changes on a branch.
 - **An agent that keeps it that way**: the rules and skills Aura installs teach your coding agent your standards, and GitHub Actions re-scans every push.
 
-Ask your coding agent: "Check my Aura score and fix the most serious issue." Or use Aura's commands in it: `/aura:scan` and `/aura:fix` in Claude Code, `/aura-scan` in Cursor and Pi, `$aura-scan` in Codex.
+Ask your coding agent: "Check my Aura score and fix the most serious issue." Or use Aura's commands in it: `/aura:check` and `/aura:fix` in Claude Code, `/aura-check` in Cursor and Pi, `$aura-check` in Codex.
 
 ## Privacy
 
@@ -37,4 +39,10 @@ Scanning runs on your machine and your repo is never uploaded. Only short, redac
 
 ## Commands
 
-`init`, `scan`, `next`, `apply`, `fix`, `guide`, `inventory`, `history`, `summary`, `login`, `whoami`, `config`, `check-staged`. Run `aura <command> --help` for options.
+`init`, `check`, `next`, `apply`, `fix`, `guide`, `inventory`, `history`, `summary`, `login`, `whoami`, `config`, `check-staged`. Run `aura <command> --help` for options.
+
+## License
+
+Aura is licensed under the [Functional Source License, Version 1.1, MIT Future License](LICENSE) (FSL-1.1-MIT). You can use it for your own projects, your company's and your clients', read its code and change it. What you can't do is offer it, or something built from it, as a product that competes with Aura. Two years after each version is released, that version becomes MIT.
+
+Everything Aura writes into your project (skills, agent rules, workflows, configs, guides) is yours, under [MIT-0](templates/LICENSE): use, change and share it freely, no attribution needed. Bundled third-party code keeps its own license ([notices](THIRD-PARTY-NOTICES.md)).

package/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,31 @@
+# Third-party notices
+
+The `getaura` CLI bundles the following open-source code into `dist/index.js`. Each keeps its own license, reproduced here as it requires.
+
+## zod
+
+https://github.com/colinhacks/zod
+
+```
+MIT License
+
+Copyright (c) 2025 Colin McDonnell
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```