Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 07:35 UTC

camunda / camunda-security-library

A repo for the new Camunda Security and Authentication library

JavaCustom license★ 4 stars⑂ 2 forkssince Apr 2026View on GitHub ↗

camunda/camunda-security-library holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (44/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

84
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

84
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 71 is calibrated to 84 on the published index scale (record calibration 2026-08-02).

Ownership

CamundaOrganization
1,553 followers219 public repossince Sep 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenio.camunda:camunda-security-library-api1.1.2-745 days ago
Mavenio.camunda:camunda-security-library-core1.1.2-745 days ago
Mavenio.camunda:camunda-security-library-validation1.1.2-475 days ago
Mavenio.camunda:camunda-security-library-spring-boot-starter1.1.2-745 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
18.7/36Commit cadence — 27/52 weeks with commits
18/18Commit volume — 925 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year925
human_commit_share0.92
days_since_last_push2
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 74 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~6.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count74
latest_release_tag1.1.2
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases6.8
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

44Weak · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11.1/22.5Commit distribution — top contributor authored 51% of commits
13.5/13.5Contributor breadth — 14 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.508
How it's scored
30.4/42Issue resolution — 72% of issues closed
27.5/30PR acceptance — 368/402 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 4/19 approved changesets -- score normalized to 2
Inputs used
merged_prs368
open_issues87
closed_issues228
prs_merged_7d3
prs_decided_7d4
prs_merged_30d11
prs_decided_30d14
issue_closed_ratio0.724
closed_unmerged_prs34
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
22.9/25Owner reach — 1,553 followers of camunda
25/25Track record — 219 public repos, account ~14 yr old
Inputs used
followers1,553
owner_typeOrganization
is_verifiedno
owner_logincamunda
public_repos219
account_age_days5,133

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on maven
35/35Publish recency — latest publish 5 days ago
20/20Version history — 74 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesio.camunda:camunda-security-library-api, io.camunda:camunda-security-library-core, io.camunda:camunda-security-library-validation, io.camunda:camunda-security-library-spring-boot-starter
ecosystemsmaven
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

77Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 4/19 approved changesets -- score normalized to 2
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.1
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages20
unassessed_packages45
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 20 resolved dependencies against OSV. 45 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 84 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.913
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes12,200
How it's scored
12.6/18One-command bootstrap — api/pom.xml, core/pom.xml, pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 82 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 6 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.82
toolchain_manifestsapi/pom.xml, core/pom.xml, pom.xml, spring-boot-starter/pom.xml, validation/pom.xml
dependency_bot_commit_share0.06
How it's scored
45/45Type-checkable code — Java (statically typed)
54.5/55Manageable file sizes — 4/457 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes76,336
source_files_sampled457
oversized_source_files4

Key facts

4GitHub stars
14contributors
925commits, last 12 months
2days since last push
74releases
1bus factor
87open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
41Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

111222212026-062026-082026-09
Major 1Minor 0Patch 4
OpenSSF Scorecard 7.1 / 10
7.1aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-10-19 07:35 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/19 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 38
RegistryPackageVersion constraintManifest
Mavenio.camunda:camunda-security-library-api${project.version}core/pom.xml
Mavencom.jayway.jsonpath:json-path—core/pom.xml
Mavenorg.slf4j:slf4j-api—core/pom.xml
Mavenorg.springframework.boot:spring-boot-dependencies${spring-boot.version}pom.xml
Mavenorg.testcontainers:testcontainers-bom${testcontainers.version}pom.xml
Mavencom.tngtech.archunit:archunit${archunit.version}pom.xml
Mavencom.tngtech.archunit:archunit-junit5-api${archunit.version}pom.xml
Mavencom.tngtech.archunit:archunit-junit5-engine${archunit.version}pom.xml
Mavencom.nimbusds:nimbus-jose-jwt${nimbus-jose-jwt.version}pom.xml
Mavencommons-validator:commons-validator1.11.0pom.xml
Mavencom.puppycrawl.tools:checkstyle${version.checkstyle}pom.xml
Mavenio.camunda:camunda-security-library-api${project.version}spring-boot-starter/pom.xml
Mavenio.camunda:camunda-security-library-core${project.version}spring-boot-starter/pom.xml
Mavenorg.springframework.boot:spring-boot—spring-boot-starter/pom.xml
Mavenorg.springframework.boot:spring-boot-autoconfigure—spring-boot-starter/pom.xml
Mavenorg.springframework:spring-context—spring-boot-starter/pom.xml
Mavenorg.springframework.boot:spring-boot-starter-validation—spring-boot-starter/pom.xml
Mavenorg.springframework.session:spring-session-core—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-config—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-web—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-core—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-crypto—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-oauth2-client—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-oauth2-core—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-oauth2-resource-server—spring-boot-starter/pom.xml
Mavenorg.springframework.security:spring-security-oauth2-jose—spring-boot-starter/pom.xml
Mavencom.nimbusds:nimbus-jose-jwt—spring-boot-starter/pom.xml
Mavenorg.springframework:spring-web—spring-boot-starter/pom.xml
Mavenorg.springframework:spring-core—spring-boot-starter/pom.xml
Mavenorg.springframework:spring-beans—spring-boot-starter/pom.xml
Mavenjakarta.annotation:jakarta.annotation-api—spring-boot-starter/pom.xml
Mavencom.fasterxml.jackson.core:jackson-core—spring-boot-starter/pom.xml
Mavencom.fasterxml.jackson.core:jackson-databind—spring-boot-starter/pom.xml
Mavencom.github.ben-manes.caffeine:caffeine—spring-boot-starter/pom.xml
Mavenio.micrometer:micrometer-core—spring-boot-starter/pom.xml
Mavenorg.slf4j:slf4j-api—spring-boot-starter/pom.xml
Mavenio.camunda:camunda-security-library-api${project.version}validation/pom.xml
Mavencommons-validator:commons-validator—validation/pom.xml
All dependencies 65

Full resolved dependency set from the GitHub dependency graph: 38 direct and 27 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Mavencom.fasterxml.jackson.core:jackson-core—direct
Mavencom.fasterxml.jackson.core:jackson-databind—direct
Mavencom.github.ben-manes.caffeine:caffeine—direct
Mavencom.jayway.jsonpath:json-path—direct
Mavencom.nimbusds:nimbus-jose-jwt—direct
Mavencom.nimbusds:nimbus-jose-jwt10.10direct
Mavencom.puppycrawl.tools:checkstyle14.3.0direct
Mavencom.tngtech.archunit:archunit—direct
Mavencom.tngtech.archunit:archunit1.5.1direct
Mavencom.tngtech.archunit:archunit-junit5-api—direct
Mavencom.tngtech.archunit:archunit-junit5-api1.5.1direct
Mavencom.tngtech.archunit:archunit-junit5-engine—direct
Mavencom.tngtech.archunit:archunit-junit5-engine1.5.1direct
Mavencommons-validator:commons-validator—direct
Mavencommons-validator:commons-validator1.11.0direct
Mavenio.camunda:camunda-security-library-api1.1.3-SNAPSHOTdirect
Mavenio.camunda:camunda-security-library-core1.1.3-SNAPSHOTdirect
Mavenio.micrometer:micrometer-core—direct
Mavenjakarta.annotation:jakarta.annotation-api—direct
Mavenorg.slf4j:slf4j-api—direct
Mavenorg.springframework.boot:spring-boot—direct
Mavenorg.springframework.boot:spring-boot-autoconfigure—direct
Mavenorg.springframework.boot:spring-boot-dependencies4.1.1direct
Mavenorg.springframework.boot:spring-boot-starter-validation—direct
Mavenorg.springframework.security:spring-security-config—direct
Mavenorg.springframework.security:spring-security-core—direct
Mavenorg.springframework.security:spring-security-crypto—direct
Mavenorg.springframework.security:spring-security-oauth2-client—direct
Mavenorg.springframework.security:spring-security-oauth2-core—direct
Mavenorg.springframework.security:spring-security-oauth2-jose—direct
Mavenorg.springframework.security:spring-security-oauth2-resource-server—direct
Mavenorg.springframework.security:spring-security-web—direct
Mavenorg.springframework.session:spring-session-core—direct
Mavenorg.springframework:spring-beans—direct
Mavenorg.springframework:spring-context—direct
Mavenorg.springframework:spring-core—direct
Mavenorg.springframework:spring-web—direct
Mavenorg.testcontainers:testcontainers-bom2.0.5direct
Mavench.qos.logback:logback-classic—indirect
Mavench.qos.logback:logback-core—indirect
Mavencom.diffplug.spotless:spotless-maven-plugin—indirect
Mavencom.diffplug.spotless:spotless-maven-plugin3.10.4indirect
Mavenjakarta.servlet:jakarta.servlet-api—indirect
Mavenorg.apache.maven.plugins:maven-checkstyle-plugin—indirect
Mavenorg.apache.maven.plugins:maven-checkstyle-plugin3.6.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.16.0indirect
Mavenorg.apache.maven.plugins:maven-dependency-plugin—indirect
Mavenorg.apache.maven.plugins:maven-dependency-plugin3.11.0indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin—indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin3.6.3indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.5.1indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin—indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.12.0indirect
Mavenorg.apache.maven.plugins:maven-release-plugin3.3.1indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.6.0indirect
Mavenorg.assertj:assertj-core—indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.6.4indirect
Mavenorg.junit.jupiter:junit-jupiter-api—indirect
Mavenorg.junit.jupiter:junit-jupiter-engine—indirect
Mavenorg.junit.jupiter:junit-jupiter-params—indirect
Mavenorg.mockito:mockito-core—indirect
Mavenorg.mockito:mockito-junit-jupiter—indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin—indirect
Mavenorg.springframework.boot:spring-boot-test—indirect
Mavenorg.springframework:spring-test—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 20 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 45 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Maven.