This repository was archived by the owner on Sep 8, 2026. It is now read-only.
docs: add repository threat model - #1
Open
msmans wants to merge 1 commit into
Open
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Adds a repository-specific threat model for
universal-analytics-python, covering its actual components, data recipients, trust boundaries, controls, deployment assumptions and prioritized attacker scenarios. Threat scenarios are hypotheses, not confirmed vulnerabilities; sensitive data handling and downstream impact are tied to demonstrated permissions and use.Validation: independent source architecture pass, direct reconciliation of material consumers, and source citation path/line checks at revision 78ee36a. Documentation only; no application execution or live infrastructure/security checks. Remaining deployment and external-control unknowns are explicit. Merge after accepting the documented boundaries and assumptions; rollback is reverting this documentation commit.