Security and privacy
Software supply chain
Building and signing releases and checking dependencies. A process plan in the repo, not a result.
Designed in a document, no code yet
What to plan for
- Dependency vulnerabilities
- Reproducible builds
- Signing keys
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Archived data comes back when the element is re-added DATA-0040
- Removal changes data in one transaction DATA-0044
- Dependency vulnerability scanning SEC-0040
- No demo or default keys in any build SEC-0049
- Release channels (stable/beta) LIC-0015
- Offline licence semantics: updates_until (reserved, enforcement open) LIC-0044
- Quarterly cost model as signed data LIC-0052
- Flat fee calculator: the quarter's cost split among paying members LIC-0073
- One flat quarterly fee for every product LIC-0061
- Early members are rewarded by their own bill falling LIC-0062
- Your bill has dropped X percent LIC-0063
- Bill change refuses an unsound history LIC-0064
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.