OWASP / OWASP/owasp-java-encoder
Add maintained code scanning and automated dependency update workflows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 541
- Forks
- 122
- Avg merge
- 9h 9m
- Merged PRs (30d)
- 1
Description
Follow-up to #90 (reviewed at 31588e1). This tracks work intentionally kept separate from the modernization PR.
Current state
As checked on 2026-09-11, GitHub reports CodeQL default setup as not-configured. The repository contains a build workflow but no checked-in CodeQL or Dependabot configuration.
The project would benefit from ongoing checks after the one-time dependency updates in #90.
Acceptance criteria
- Choose one maintained CodeQL setup (default or advanced) appropriate for this Maven reactor; configure PR/default-branch and scheduled analysis as appropriate, without duplicate scan jobs.
- Confirm analysis includes the intended Java modules and relevant workflow code, and document the optional Jakarta test application's coverage.
- Establish dependency/Actions update automation with sensible grouping and cadence; cover the optional test-app POM as well as the published library modules.
- Treat the deliberately pinned Felix 5.6.12 OSGi R6 test fixture as a documented compatibility fixture: do not silently upgrade it away, and review any applicable advisories rather than blanket-suppressing findings.
- Review dependency alerts by runtime/test/build scope; document ownership and a triage process without disabling meaningful security checks.
- Preserve least-privilege permissions, keep secrets away from untrusted PR execution, and validate action changes with actionlint.
- Require the normal tests and consumer-contract checks for automated update PRs; do not enable unattended merges of packaging-sensitive changes.
Reference: GitHub code-scanning setup documentation.
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.
Research direction
Review the existing build workflow and Maven reactor, including the optional test application's POM and the pinned Felix 5.6.12 fixture. Then check the CodeQL and dependency-update requirements, least-privilege permissions, and actionlint validation. Done means maintained workflows cover the intended modules and update scopes, preserve required tests and consumer-contract checks, and document triage and compatibility decisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100