feat: add SpringNullGuard — safe Spring nullability to JSpecify migration agent - #14
Open
spargy4050v wants to merge 1 commit into
Open
feat: add SpringNullGuard — safe Spring nullability to JSpecify migration agent#14spargy4050v wants to merge 1 commit into
spargy4050v wants to merge 1 commit into
Conversation
spargy4050v
force-pushed
the
rebuild/springnullguard-clean
branch
from
August 8, 2026 02:50
0ba9c11 to
d66ee5b
Compare
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.
SpringNullGuard
SpringNullGuard is a migration agent for safely modernizing legacy Spring null-safety annotations to JSpecify.
Instead of performing a textual annotation replacement, it uses structural Java analysis and verification to preserve nullability semantics, including JSpecify
TYPE_USEplacement.What it does
Real-world validation
A Bezkoder Spring Boot project is included under:
real-world/bezkoder-sb3/The upstream project did not contain the target Spring nullability annotation, so one representative
org.springframework.lang.Nullableannotation was intentionally seeded for evaluation and is explicitly disclosed in the submission.Migration performed: