Jb1/16 cryptography models libraries and queries migration #18
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
…dels and old_models.
…python models, inventory, and example alerts.
…ventory models. Added some example old models.
Changing metadata to under python namespace
…snapshot-repositories-test Java: Add test re: buildless mode interaction with snapshot repositories
Swift: Fix bug in taint flow through string interpolation
Ruby: Collapse DIL stages
C#: Roslyn-based stub generation
…locations for RegExpTerms.
Update CSV framework coverage reports
…egex-locations Python: Improve source-location information for RegExpTerms.
…prov Java: Consider AssignOps in ArithExpr
Data flow: Performance improvements
We never claimed to support anything < 1.5.0, and compiling with -language-version 1.4 fails as it's not meant to support sealed classes. If we build 1.4.32 with -language-version 1.5 using a 2.0 compiler, then the resulting plugin also fails.
Otherwise builds with Kotlin 2 won't work with older compilers.
Now that we have array content, this is a more principled approach than having a special case data step.
…fine grain the LocalUserInput threat models.
CPP: Fix some use after free FPs.
…-and-double-free C++: Promote `cpp/double-free` and `cpp/use-after-free` to Code Scanning
Kotlin: Specify language version when compiling for old compilers
…ilation C#: Extract compilation DB entity in standalone mode
…rces Java: Introduce a class of dataflow nodes for the threat modeling.
Swift: Replace two additional taint steps with implicit reads
Swift: Model .description, .debugDescription more generally
Swift: Update summary queries
ropwareJB
deleted the
jb1/16-cryptography-models-libraries-and-queries-migration
branch
bdrodes
pushed a commit
that referenced
this pull request
Jan 9, 2025
feat(triggers): New query and support for trigger-based severity decisions
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.
No description provided.