Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 14:59 UTC

camunda / dmn-scala

DMN engine written in Scala

ScalaApache-2.0★ 42 stars⑂ 15 forkssince Oct 2017View on GitHub ↗

camunda/dmn-scala holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Sustainability & Governance (56/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

73
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 64 is calibrated to 73 on the published index scale (record calibration 2026-08-02).

Ownership

CamundaOrganization
1,524 followers217 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
Mavenorg.camunda.bpm.extension.dmn.scala:dmn-enginepoints to another repo — not scored1.12.2-3062 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
19.4/36Commit cadence28/52 weeks with commits
17.7/18Commit volume92 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year92
human_commit_share0.66
days_since_last_push5
active_weeks_last_year28
How it's scored
27/27Ships releases31 releases published
36/36Release recencylatest release 62 days ago
19.8/27Release cadencea release every ~59.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count31
latest_release_tag1.12.2
releases_from_tagsno
days_since_latest_release62
mean_days_between_releases59.7

Community & Adoption

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

57Moderate · 17% of overall
How it's scored
26.2/60Stars42 stars
9.6/25Forks15 forks
7.6/15Watchers24 watchers
Inputs used
forks15
stars42
watchers24
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/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_contributingno
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.9/22.5Commit distributiontop contributor authored 78% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.78
How it's scored
24.6/42Issue resolution59% of issues closed
21.1/30PR acceptance216/307 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 2/9 approved changesets -- score normalized to 2
Inputs used
merged_prs216
open_issues24
closed_issues34
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.586
closed_unmerged_prs91
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
22.9/25Owner reach1,524 followers of camunda
25/25Track record217 public repos, account ~13 yr old
Inputs used
followers1,524
owner_typeOrganization
is_verifiedno
owner_logincamunda
public_repos217
account_age_days5,098

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests8 out of 8 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsdmn, decision-engine, camunda-plugin, zeebe-worker
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 2/9 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
7.4/25Indirect dependencies free of known advisories2 affected: com.fasterxml.jackson.core:jackson-core 2.21.1 (high 7.5), com.fasterxml.jackson.core:jackson-databind 2.21.1 (high 8.1)
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories11
affected_packages2
assessed_packages14
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the maven:org.camunda.bpm.extension.dmn.scala:dmn-engine@1.12.2 runtime dependency closure — what installing the published package pulls in — 14 packages. 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.

64Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.camunda.io/llms.txt)
40/40Legible commit history60 of 66 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.camunda.io/llms.txt
legible_history_share0.909
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrappom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingScala (statically typed)
0/10Reproducible environment
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance32 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.02
toolchain_manifestspom.xml
dependency_bot_commit_share0.32
How it's scored
45/45Type-checkable codeScala (statically typed)
55/55Manageable file sizes0/41 source files over 60KB
Inputs used
primary_languageScala
largest_source_bytes20,588
source_files_sampled41
oversized_source_files0

Key facts

42GitHub stars
19contributors
92commits, last 12 months
5days since last push
31releases
1bus factor
24open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • maven package 'org.camunda.bpm.extension.dmn.scala:dmn-engine' points at a different repository (https://github.com/camunda-community-hub/dmn-scala.git); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
21Releases

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.

03581013151522018-092022-032025-08
Major 0Minor 10Patch 11

Each point covers 7 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-09-13 14:59 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests8 out of 8 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 2/9 approved changesets -- score normalized to 2
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Mavenorg.camunda.feel:feel-engine${feel.version}pom.xml
Mavenorg.camunda.bpm.model:camunda-dmn-model${camunda-model-api.version}pom.xml
Mavenorg.scala-lang:scala-library${scala.version}pom.xml
Mavenorg.slf4j:slf4j-api2.0.19pom.xml
Mavenorg.apache.logging.log4j:log4j-api${log4j.version}pom.xml
Mavenorg.apache.logging.log4j:log4j-core${log4j.version}pom.xml
Mavenorg.apache.logging.log4j:log4j-slf4j2-impl${log4j.version}pom.xml
Mavenorg.scalatest:scalatest_2.133.2.20pom.xml
Mavenorg.camunda.feel:feel-enginepom.xml
Mavenorg.camunda.bpm.model:camunda-dmn-modelpom.xml
Mavenorg.slf4j:slf4j-apipom.xml
All dependencies 24

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

RegistryPackageVersionRelation
Mavenorg.apache.logging.log4j:log4j-apidirect
Mavenorg.apache.logging.log4j:log4j-api2.25.4direct
Mavenorg.apache.logging.log4j:log4j-coredirect
Mavenorg.apache.logging.log4j:log4j-core2.25.4direct
Mavenorg.apache.logging.log4j:log4j-slf4j2-impldirect
Mavenorg.apache.logging.log4j:log4j-slf4j2-impl2.25.4direct
Mavenorg.camunda.bpm.model:camunda-dmn-modeldirect
Mavenorg.camunda.bpm.model:camunda-dmn-model7.24.0direct
Mavenorg.camunda.feel:feel-enginedirect
Mavenorg.camunda.feel:feel-engine1.22.0direct
Mavenorg.scala-lang:scala-library2.13.18direct
Mavenorg.scalatest:scalatest_2.13direct
Mavenorg.scalatest:scalatest_2.133.2.20direct
Mavenorg.slf4j:slf4j-apidirect
Mavenorg.slf4j:slf4j-api2.0.19direct
Mavencom.mycila:license-maven-plugin5.1.2indirect
Mavennet.alchim31.maven:scala-maven-plugin4.9.10indirect
Mavenorg.antipathy:mvn-scalafmt_2.120.7_1.5.1indirect
Mavenorg.apache.maven.plugins:maven-antrun-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-dependency-plugin3.11.0indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.6.0indirect
Mavenorg.codehaus.mojo:build-helper-maven-plugin3.6.1indirect
Mavenorg.codehaus.mojo:clirr-maven-plugin2.8indirect
Mavenorg.scalatest:scalatest-maven-plugin2.2.0indirect
Dependency advisories 2

Installing maven:org.camunda.bpm.extension.dmn.scala:dmn-engine@1.12.2 pulls in 14 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
com.fasterxml.jackson.core:jackson-core2.21.1indirecthigh13.1.4
com.fasterxml.jackson.core:jackson-databind2.21.1indirecthigh103.2.1

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 statisticsMaven.