|
2 | 2 |
|
3 | 3 | [](https://hex.pm/packages/sigra) |
4 | 4 | [](https://hexdocs.pm/sigra) |
| 5 | +[](https://github.com/szTheory/sigra/actions/workflows/ci.yml) |
5 | 6 |
|
6 | 7 | **Production-minded authentication for Phoenix 1.8+** — sessions, passwords, email flows, OAuth, MFA, passkeys, optional organizations and admin tooling — without treating security-sensitive code as throwaway scaffolding. |
7 | 8 |
|
@@ -62,7 +63,7 @@ flowchart TD |
62 | 63 | 1. **Dependency** (`mix.exs`): |
63 | 64 |
|
64 | 65 | ```elixir |
65 | | - {:sigra, "~> 0.2.0"} |
| 66 | + {:sigra, "~> 0.2"} |
66 | 67 | ``` |
67 | 68 |
|
68 | 69 | 2. **Scaffold** (from app root; names must match your domain): |
@@ -159,19 +160,14 @@ One clause each — depth lives in HexDocs and the guides linked in the next sec |
159 | 160 | | **Enumeration** | Safer defaults on account discovery flows (details in HexDocs per flow). | |
160 | 161 | | **Step-up** | Sudo / MFA challenge patterns integrate with Phoenix plugs and LiveView mounts as generated. | |
161 | 162 |
|
162 | | -For threat-model detail and per-flow guarantees, use **HexDocs** and the verification narratives shipped with each release milestone — the README stays a map, not a spec. |
| 163 | +For threat-model detail and per-flow guarantees, use **HexDocs** and the guides above — the README stays a map, not a spec. |
163 | 164 |
|
| 165 | +## Release evidence (maintainers and auditors) |
164 | 166 |
|
165 | | -## Production readiness & GA evidence |
| 167 | +Sigra keeps an **evidence hub** (what we ran versus waived for GA cuts, how CI maps to human UAT rows, and pointers to planning artifacts on GitHub). That material is **not** a compliance certificate for your application — integration and deployment risk stay with the **host**. |
166 | 168 |
|
167 | | -Sigra's **Executed** items are procedures or artifacts we actually ran for the v1.4 milestone; **Waived** items are matrix rows we consciously did not re-run for that cut, with documented substitutes where applicable. Integration, deployment, and product-specific threats remain with the **host application**—this narrative is **not a compliance certification**, only an honest map to evidence. |
168 | | - |
169 | | -- [v1.4 requirements closure (tag snapshot)](https://github.com/sztheory/sigra/blob/v0.2.0/.planning/milestones/v1.4-REQUIREMENTS.md) |
170 | | -- [v1.4 GA / UAT matrix (tag snapshot)](https://github.com/sztheory/sigra/blob/v0.2.0/.planning/v1.4-GA-UAT.md) |
171 | | -- [Milestone index (tag snapshot)](https://github.com/sztheory/sigra/blob/v0.2.0/.planning/MILESTONES.md) |
172 | | -- [How UAT rows relate to CI substitutes](uat-ci-coverage.md) (source: `docs/uat-ci-coverage.md`) |
173 | | - |
174 | | -On **hexdocs.pm/sigra**, the packaged hub lives at [`ga-evidence` for 0.2.0](https://hexdocs.pm/sigra/0.2.0/ga-evidence.html) so GitHub-first readers and HexDocs readers see the same pointers. |
| 169 | +- **[GA evidence and audit posture](docs/ga-evidence.md)** — router page; same content ships on [HexDocs](https://hexdocs.pm/sigra/ga-evidence.html). |
| 170 | +- **[UAT versus CI coverage](docs/uat-ci-coverage.md)** — machine versus human boundaries. |
175 | 171 |
|
176 | 172 | Coordinated disclosure: [SECURITY.md](SECURITY.md). |
177 | 173 |
|
|
0 commit comments