Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-21 11:50 UTC

mojohaus / taglist-maven-plugin

Reports on TODO, FIXME and other tags left in the source

JavaNo license detected★ 10 stars⑂ 7 forkssince May 2015View on GitHub ↗
KindPluginLibraryhow this is determined

mojohaus/taglist-maven-plugin holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (81/100) and lowest on Community & Adoption (27/100). It was last updated 8 days ago. 3 contributors account for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

MojoHausOrganization
104 followers95 public repossince Mar 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.codehaus.mojo:taglist-maven-plugin3.2.2-11270 days ago

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 8 days ago
11.1/36Commit cadence16/52 weeks with commits
11.9/18Commit volume20 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year20
human_commit_share0.46
days_since_last_push8
active_weeks_last_year16
How it's scored
27/27Ships releases5 releases published
16.2/36Release recencylatest release 270 days ago
12.6/27Release cadencea release every ~349.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagtaglist-maven-plugin-3.2.2
releases_from_tagsno
days_since_latest_release270
mean_days_between_releases349.7
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?

27At Risk · 17% of overall
How it's scored
15.5/60Stars10 stars
6.5/25Forks7 forks
6.2/15Watchers14 watchers
Inputs used
forks7
stars10
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

81Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16.8/22.5Commit distributiontop contributor authored 26% of commits
13.5/13.5Contributor breadth16 contributors
10/10OpenSSF Scorecard: Contributorsproject has 21 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled16
top_contributor_share0.255
How it's scored
42/42Issue resolution100% of issues closed
20.6/30PR acceptance105/153 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/7 approved changesets -- score normalized to 1
Inputs used
merged_prs105
open_issues0
closed_issues41
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs48
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 domainverified-domain status not read for this organization
14.5/25Owner reach104 followers of mojohaus
25/25Track record95 public repos, account ~11 yr old
Inputs used
followers104
owner_typeOrganization
is_verified
owner_loginmojohaus
public_repos95
account_age_days4,182
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on maven
26/35Publish recencylatest publish 270 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesorg.codehaus.mojo:taglist-maven-plugin
ecosystemsmaven
any_deprecatedno
min_days_since_publish270

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 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
14/20OpenSSF Scorecard: CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.mojohaus.org/taglist-maven-plugin/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsjava, maven, maven-plugin, mojohaus
has_wikino
homepagehttps://www.mojohaus.org/taglist-maven-plugin/
docs_sitehttps://www.mojohaus.org/taglist-maven-plugin/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 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
1.8/2.5CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 1/7 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 21 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
8.1/35Direct dependencies free of known advisories2 affected: org.apache.maven:maven-core 3.6.3 (critical 9.1), org.codehaus.plexus:plexus-utils 4.0.2 (high)
3.2/25Indirect dependencies free of known advisories5 affected: org.apache.maven.shared:maven-shared-utils 3.2.1 (critical 9.8), commons-beanutils:commons-beanutils 1.9.4 (high 8.8), commons-io:commons-io 2.5 (high 7.5), +2 more
17.2/40No advisories left outstanding7 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,974 days ago
Inputs used
sourceosv
advisories9
affected_packages7
assessed_packages68
unassessed_packages0
affected_by_severitycritical 2, high 3, moderate 2
direct_affected_packages2
Matched the maven:org.codehaus.mojo:taglist-maven-plugin@3.2.2 runtime dependency closure — what installing the published package pulls in — 68 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
4.6/40Legible commit history4 of 46 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.087
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 checkingJava (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance54 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
toolchain_manifestspom.xml
dependency_bot_commit_share0.54
How it's scored
45/45Type-checkable codeJava (statically typed)
55/55Manageable file sizes0/33 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes22,574
source_files_sampled33
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

10GitHub stars
16contributors
20commits, last 12 months
8days since last push
5releases
3bus factor
0open 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 ★ / 7 ⇿
0Stars
7Forks
1Releases

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.

234567722015-092019-062023-04
Major 0Minor 0Patch 0

Each point covers 7 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-08-21 11:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests18 out of 24 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/7 approved changesets -- score normalized to 1
10Contributorsproject has 21 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Mavenorg.codehaus.plexus:plexus-utils4.0.3pom.xml
Mavenorg.apache.maven.reporting:maven-reporting-api${reportingApiVersion}pom.xml
Mavenorg.apache.maven.reporting:maven-reporting-impl${reportingImplVersion}pom.xml
Mavenorg.apache.maven.doxia:doxia-sink-api${doxiaVersion}pom.xml
Mavenorg.apache.commons:commons-lang33.20.0pom.xml
Mavenorg.codehaus.plexus:plexus-utilspom.xml
Mavenorg.codehaus.plexus:plexus-xml3.0.1pom.xml
All dependencies 25

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

RegistryPackageVersionRelation
Mavenorg.apache.commons:commons-lang33.20.0direct
Mavenorg.apache.maven.doxia:doxia-sink-api2.1.0direct
Mavenorg.apache.maven.reporting:maven-reporting-api4.0.0direct
Mavenorg.apache.maven.reporting:maven-reporting-impl4.0.0direct
Mavenorg.codehaus.plexus:plexus-utilsdirect
Mavenorg.codehaus.plexus:plexus-utils4.0.3direct
Mavenorg.codehaus.plexus:plexus-xml3.0.1direct
Mavenorg.apache.maven.plugin-testing:maven-plugin-testing-harness3.5.1indirect
Mavenorg.apache.maven.plugin-tools:maven-plugin-annotationsindirect
Mavenorg.apache.maven.plugins:maven-javadoc-pluginindirect
Mavenorg.apache.maven.plugins:maven-jxr-pluginindirect
Mavenorg.apache.maven.plugins:maven-surefire-pluginindirect
Mavenorg.apache.maven.resolver:maven-resolver-connector-basic1.4.1indirect
Mavenorg.apache.maven.resolver:maven-resolver-transport-http1.4.1indirect
Mavenorg.apache.maven:maven-artifactindirect
Mavenorg.apache.maven:maven-compatindirect
Mavenorg.apache.maven:maven-coreindirect
Mavenorg.apache.maven:maven-modelindirect
Mavenorg.apache.maven:maven-plugin-apiindirect
Mavenorg.codehaus.modello:modello-maven-plugin1.0.0indirect
Mavenorg.codehaus.mojo:taglist-maven-plugin3.2.3-SNAPSHOTindirect
Mavenorg.junit.jupiter:junit-jupiter-apiindirect
Mavenorg.junit.jupiter:junit-jupiter-paramsindirect
Mavenorg.junit.vintage:junit-vintage-engineindirect
Mavenorg.slf4j:slf4j-simple1.7.36indirect
Dependency advisories 7

Installing maven:org.codehaus.mojo:taglist-maven-plugin@3.2.2 pulls in 68 packages, direct and transitive: 7 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
org.apache.maven:maven-core3.6.3directcritical13.8.1
org.apache.maven.shared:maven-shared-utils3.2.1indirectcritical13.3.3
org.codehaus.plexus:plexus-utils4.0.2directhigh14.0.3
commons-beanutils:commons-beanutils1.9.4indirecthigh12.0.0-M2
commons-io:commons-io2.5indirecthigh22.14.0
com.google.guava:guava25.1-androidindirectmoderate232.0.0-android
org.iq80.snappy:snappy0.4indirectmoderate10.5

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.