Understand beemdevelopment/aegis's source layout and find a starting point for your task using the saved repository evidence.
Detailed import-graph metrics were not captured for this report.
Files at d6f4e5925a97 · descriptions are AI-written.
The descriptions and the file list come from different revisions. Check responsibilities against source.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Suggested by the saved analysis. Verify the proposed change against these source files.
Use a nearby test as a pattern. Read the root manifest or contribution guide for the correct test command. These suggestions use file names, not verified execution paths.
Inspect the relevant configuration and the commands it runs before changing the workflow. These suggestions use file names, not verified execution paths.
File paths come from a snapshot of up to 500 captured paths; an omitted file may still exist.
Main application entry point; initializes Dagger Hilt, theme configuration, and all core app infrastructure.
Room database schema definition; contains all persistent data models for vault entries, audit logs, and settings.
Cryptographic key management for vault encryption; handles SCrypt derivation and encrypted storage in Android Keystore.
Abstract base class for all OTP implementations (TOTP, HOTP, MOTP, YAOTP); core token generation logic.
Centralized SharedPreferences wrapper for all user settings, themes, sorting, and security policies.
Build configuration with Gradle plugins (Hilt, Protobuf, aboutLibraries), dependencies, and SDK targets.
This repo is in good health with CI, tests, and active maintenance.
How maintainable the code looks — from complexity, code issues, test presence, file size, and hotspot load. It grades the shape of the code, not defect risk, and doesn't replace review.
Provider: GitHub Actions
62 test files detected
Stack: JUnit
Where: app/src/test/resources/com/beemdevelopment/aegis/importers · app/src/test/java/com/beemdevelopment/aegis/otp · app/src/test/java/com/beemdevelopment/aegis/crypto/otp
62 test files / 246 source files. This is a file-count ratio, not real line coverage — set up Codecov for authoritative numbers.
CodeQL
Files edited often AND hard to reason about. Churn = recent commit frequency, Complexity = branches and nesting, Risk = both combined. These are the highest-leverage targets for refactoring or testing.
Files that change often and are complex tend to accumulate more bugs
Static analysis on sampled source files (up to 15 files).