Repository navigation
Clarify PTxray benefits, open source, and assessment safety - #22
Merged
Merged
Conversation
John-PTS
marked this pull request as ready for review
September 20, 2026 00:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The public README moves from a brief introduction directly into release downloads and commands, leaving the benefits and open-source license difficult to discover. This revision leads with the questions PTxray helps answer, the evidence and reports users receive, and the Apache-2.0 assessment code. Release history has a secondary section at the end.
Safety is explained through specific behavior: no system configuration changes or remediation, no network calls during assessment, no assessment-data uploads, separate disclosed acquisition, and verifiable signed releases. Privileged execution, local writes, manual evidence gaps, vendor inputs, and report-sharing limits remain explicit.
Validation: all 22 public-page tests pass; release version/count checks, README section/local links, and whitespace checks pass.
Suggested GitHub About description for review: