DevNav

DevNav provides a maintained upgrade path through its self-update mechanism (dev update / Shift+U) and through the supported package-manager channels. The updater verifies release SHA-256 checksums and preserves the user's local configuration. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/powershell/DevNav.psm1

The project uses GitHub Issues as its public issue tracker for individual issues. https://github.com/JacobOptimiza/dev-nav/issues

No vulnerability reports have been resolved by DevNav in the last 12 months, so no reporter credit has been due during the applicable period. SECURITY.md documents that future reporters will be credited in the security advisory and release notes unless they prefer anonymity.

SECURITY.md documents DevNav's vulnerability-response process: private reporting through GitHub Private Vulnerability Reporting, acknowledgement within seven days, assessment of validity and impact, remediation with a regression test where practical, release of the fix, and coordinated disclosure through a GitHub security advisory. https://github.com/JacobOptimiza/dev-nav/blob/main/SECURITY.md

CONTRIBUTING.md defines mandatory coding standards for Rust, PowerShell and JavaScript, including formatting, linting, error handling, testing, state-changing PowerShell commands, dependency policy and pinned GitHub Actions. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/CONTRIBUTING.md#coding-standards

CI automatically enforces the selected coding standards using cargo fmt, cargo clippy with warnings denied, PSScriptAnalyzer, Pester, cargo-deny, and the repository's automated validation gates. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/ci.yml

The native Rust build honors externally supplied compiler/linker configuration. The repository adds /Brepro for deterministic MSVC linking, while an explicit RUSTFLAGS environment variable takes precedence and is therefore preserved rather than replaced. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.cargo/config.toml

When debugging information is requested through CARGO_PROFILE_RELEASE_DEBUG, the build produces dev.pdb and the source installation preserves the PDB next to the installed dev.exe. Residual or stale PDB files are removed so only symbols produced by the current build are installed. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/install.ps1

DevNav is built as a single root Cargo package/workspace. CI, source installation and release flows use root Cargo build invocations and do not recursively build subdirectories with cross-dependencies. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/Cargo.toml

Two clean isolated builds from the same source produce bit-for-bit identical dev.exe binaries. MSVC reproducibility is enabled with /Brepro, and scripts/verify-build-repeatability.ps1 independently builds the source twice and compares SHA-256 hashes in CI. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/scripts/verify-build-repeatability.ps1

DevNav can be easily installed and uninstalled using commonly-used Windows conventions, including per-user Inno Setup installers, install.ps1, Scoop, and the npm bootstrap package. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/installer/DevNav.iss

DevNav is a Windows-only application. POSIX installation variables such as DESTDIR do not apply to its supported platform. The Inno Setup installer provides the normal Windows destination selection mechanism and supports the /DIR override, while Scoop and npm follow their package-manager conventions.

CONTRIBUTING.md documents the development prerequisites and the exact commands required to build DevNav and run the same Rust, PowerShell, JavaScript, coverage, dependency-policy and repeatability gates used by CI. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/CONTRIBUTING.md

External Rust dependencies are listed in machine-processable Cargo.toml and Cargo.lock files and are policy-checked with cargo-deny. The npm bootstrap has zero runtime dependencies. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/Cargo.lock

Dependabot checks Cargo and GitHub Actions dependencies weekly, while cargo-deny checks security advisories, bans, licenses and dependency sources in CI on pushes and pull requests. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/dependabot.yml

Externally-maintained components are managed through Cargo and standard package-manager mechanisms, making their versions directly identifiable and updateable. Dependabot identifies dependency updates and cargo-deny checks known Rust dependency advisories in CI.

DevNav continuously tests against its supported toolchains and treats deprecation warnings as CI failures where applicable. Rust is checked with clippy using -D warnings, PowerShell with PSScriptAnalyzer, and the npm bootstrap is tested on supported Node.js release lines 22, 24 and 26. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/ci.yml

The automated test suites run on every pull request and every push to main and produce pass/fail results. CI covers Rust, PowerShell, npm bootstrap/distribution behavior, coverage gates, build repeatability and installer smoke tests. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/ci.yml

An audit of functional bug fixes within the applicable last-six-month period found that five of six fixes added regression tests, for an 83% regression-test rate, exceeding the required 50%.

FLOSS automated coverage tooling enforces at least 80% coverage for each applicable implementation language in CI. Current verified results are Rust production-only 87.60% lines / 86.30% regions, PowerShell 83.79% lines / 84.16% commands, and the npm bootstrap 93.79% lines. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/ci.yml

CONTRIBUTING.md contains a formal written testing policy requiring appropriate automated tests for major new functionality and regression tests for bug fixes when reasonably practical, with all applicable tests required to pass before merge. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/CONTRIBUTING.md#testing-policy

The documented contribution instructions explicitly state that major new functionality must include appropriate automated tests and that bug fixes must include regression tests when reasonably practical. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/CONTRIBUTING.md#testing-policy

CI uses strict warning and lint settings where practical: Rust clippy runs with -D warnings, cargo check covers all targets, and PowerShell is parsed and analyzed with PSScriptAnalyzer. These checks must remain clean before merge. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/ci.yml

DevNav implements applicable secure-design principles including explicit trust boundaries, local least-privilege execution, separation between the native navigator and command-executing PowerShell integration, validation of untrusted inputs, restricted update sources, and documented residual limitations. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/ARCHITECTURE.md

DevNav does not implement its own cryptographic algorithms and does not depend on cryptographic algorithms or modes with known serious weaknesses. Network update access uses the platform HTTPS/TLS stack, and downloaded release artifacts are integrity-checked with SHA-256. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/SECURITY.md

DevNav implements no custom cryptographic protocol or cipher suite. HTTPS/TLS is delegated to the Windows/.NET platform TLS stack, which negotiates supported cryptographic algorithms rather than locking DevNav to a single TLS algorithm. SHA-256 is used separately for artifact integrity. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

DevNav does not process authentication credentials or private cryptographic keys, so this criterion is not applicable.

All DevNav network communications use HTTPS. Network access occurs only through the PowerShell layer against github.com and api.github.com for update checks, downloads, and installation; the Rust binary performs no network access. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

DevNav's network communications use HTTPS to GitHub through the Windows/.NET platform TLS stack. GitHub requires TLS 1.2 or newer, and DevNav contains no code that downgrades or overrides the platform TLS configuration. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

DevNav relies on the default TLS certificate validation provided by the Windows/.NET platform stack for all HTTPS communications. No DevNav code disables, bypasses, or replaces certificate verification. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

DevNav uses the platform HTTPS stack with default TLS certificate verification, so certificate validation occurs as part of the TLS handshake before HTTP request data is transmitted. DevNav does not transmit authentication credentials or other private HTTP headers, and no certificate-validation bypass is present. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

DevNav release artifacts are cryptographically signed with Sigstore cosign keyless using GitHub Actions OIDC. All 12 distributed artifacts of v0.13.0 have public .sigstore.json verification bundles under signatures/v0.13.0/, mapped to their SHA-256 digests by index.json. SIGNING.md documents the expected OIDC issuer and certificate identity and provides reproducible cosign verify-blob instructions. The signatures were verified against the immutable v0.13.0 release artifacts, and no persistent private signing key exists on the distribution site. Future releases are automatically signed by the release workflow before publication.

DevNav validates potentially untrusted inputs using restrictive parsing and allowlists where applicable. Update inputs and release information are validated before use, downloads are restricted to expected release sources, and the config.tsv parser is additionally fuzz-tested with ClusterFuzzLite. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/powershell/DevNav.psm1

DevNav applies multiple hardening mechanisms: memory-safe Rust with unsafe code confined to narrow Win32 boundaries, hardened release settings, dependency screening with cargo deny, fuzzing and regression testing of externally influenced input, SHA-pinned GitHub Actions, minimal workflow permissions, reproducible builds, restricted HTTPS update sources, and Sigstore-signed release artifacts. The audit and residual limitations are documented publicly. https://github.com/JacobOptimiza/dev-nav/blob/main/HARDENING.md

ASSURANCE.md provides the project's evidence-based assurance case, while ARCHITECTURE.md and SECURITY.md document the threat surface and trust boundaries. The assurance case links claims to automated build, test, dependency, static-analysis, fuzzing and release-integrity evidence and explicitly records residual limitations. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/ASSURANCE.md

CodeQL performs security-oriented static analysis for Rust, GitHub Actions and JavaScript/TypeScript on pull requests, pushes to main, and a scheduled weekly run. Results are uploaded to GitHub code scanning. https://github.com/JacobOptimiza/dev-nav/blob/09d20cba4892ff4e6965f9038a71492b57ef1c70/.github/workflows/codeql.yml

DevNav does not produce application software written in a memory-unsafe native language such as C or C++. Its native application core is implemented in Rust, with PowerShell/JavaScript/installer scripting for integration and packaging, so this memory-unsafe-language criterion is not applicable.