Screen Compiler is NoWayOS's build-time tool that converts React screens, written to a documented subset, into native Rust UI code for NoWayOS. If you find a security flaw in it, please tell us privately, so that we can fix it before anyone else can use it.
Please do not open a public issue, pull request or discussion. Report it privately, either:
- through GitHub's private vulnerability reporting: Report a vulnerability on this repository's Security tab; or
- by email to security@nowayos.com.
Please tell us what is affected (crate, command, commit or release), how to
reproduce it — ideally with the smallest .tsx file that shows it — and what
an attacker could do with it. Use synthetic screens only: never send personal
data or anyone's real application code.
In scope: the code in this repository — the converter, its crates and its
build tooling — on main and in each supported release, and the Rust it
generates: a flaw in the generator that puts a security problem into the code
it writes, and so into every device built from it, is a flaw in Screen Compiler.
Out of scope:
- Running Screen Compiler on
.tsxfiles from outside your team. It is a build-time tool for screens you write yourself, and it is documented as not safe on hostile input: some pathologically nested files make it use excessive time and memory. - Third-party code, including the TSX parser and our other Rust dependencies. Please report those to their maintainers — and tell us too, if Screen Compiler's use of them is affected.
- NoWayOS, which has its own security policy.
- To acknowledge your report within 5 working days.
- To give you our assessment — whether we consider it a vulnerability, and how severe — within 15 working days.
- To keep you informed at least every 30 days until it is resolved.
- To agree a disclosure date with you: by default when the fix is released, and no later than 90 days after your report unless we both agree otherwise.
- To credit you in the advisory, by the name you choose, unless you would rather not be credited.
Until the first release, only main is supported. Once releases begin, each
release states how long it receives security fixes.
Each fixed vulnerability gets a security advisory where this repository is
hosted, and a line in the release notes' security changes. If a crate from this
repository is published on crates.io, the advisory also goes to the RustSec
advisory database, which cargo audit and cargo deny read. An advisory says
what is affected, how severe it is, the fixed version, any workaround, and who
reported it.