ulisesbocchio/jasypt-spring-boot

Jasypt integration for Spring boot

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on May 27th, 2015
Open Issues & Pull Requests: 77 (+0)
GitHub issues: Enabled
Number of forks: 548
Total Stargazers: 3,087 (+0)
Total Subscribers: 86 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.0 days
Mean response time: 81.5 days
90th percentile: 279.1 days
Tracked items: 26

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 519 days
Stale 30+ days: 20
Stale 90+ days: 17

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs clarification (2)
  • bug (1)
  • help wanted (1)
  • needs investigation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Jasypt Spring Boot is a Spring Boot starter that adds encryption support for property sources in Spring applications.

The tool solves the problem of securing sensitive configuration values by integrating Jasypt encryption into Spring's property resolution system. It works by intercepting property sources across the entire Spring Environment and decrypting encrypted values transparently at runtime. Developers can mark sensitive properties with encryption, and the tool handles decryption automatically without requiring changes to application code that reads those properties.

Adoption depends on your application structure and needs. If you use the standard `@SpringBootApplication` or `@EnableAutoConfiguration` annotations, you can simply add the starter dependency and encryption is enabled across all property sources with no additional configuration. For applications that do not use these annotations, you can add the `@EnableEncryptableProperties` annotation to your configuration class to enable encryption globally, or use `@EncryptablePropertySource` annotations for fine-grained control over which property sources support encryption. This third approach mirrors Spring's standard `@PropertySource` annotation pattern and allows you to selectively encrypt only specific configuration files. A fourth method using custom environment classes is available for special cases. The tool supports encryption across system properties, environment variables, command-line arguments, properties files, YAML files, and custom property sources.

The project maintains active engagement with its codebase through regular updates and releases. Development includes ongoing refinement of integration patterns, as evidenced by the evolution from earlier environment implementations to the current `StandardEncryptableEnvironment` and `StandardEncryptableServletEnvironment` classes. The tool has expanded its capabilities over time, such as adding YAML file support to the `@EncryptablePropertySource` annotation. The project continues to track compatibility with current Java and Spring Boot versions, requiring Java 17 and Spring Boot 3.5 or later.