spring-projects / spring-projects/spring-security
Null safety via JSpecify
@rwinch is already working on this.
Since Jul 15, 2025.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Spring Security should adopt JSpecify for Null safety as is done in Spring Framework
Related https://github.com/spring-projects/spring-framework/issues/28797
Notes on Changes
Prior to this work, passwords were sometimes treated as never null, but the reality is that they could be null (when clearCredentials was invoked). This inconsistency was also present in APIs (e.g. PasswordEncoder) that produced and consumed passwords. The semantic meaning of a null password is now clearly defined as no password for the user.
NOTE: This is done in the parent issue vs each module because things like nullability of passwords impacts more than just the core project where the API is defined.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.