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

radkovo / jStyleParser

jStyleParser is a CSS parser written in Java. It has its own application interface that is designed to allow an efficient CSS processing in Java and mapping the values to the Java data types. It parses CSS 2.1 style sheets into structures that can be efficiently assigned to DOM elements. It is intended be the primary CSS parser for the CSSBox library. While handling errors, it is user agent conforming according to the CSS specification.

Java · HTML · CSSLGPL-3.0★ 97 stars⑂ 53 forkssince Jan 2014View on GitHub ↗

radkovo/jStyleParser holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (61/100) and lowest on Vitality (6/100). It was last updated 211 days ago. A single contributor accounts for most of its recent work.

42
overall / 100
Weak

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.

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

Ownership

Radek BurgetPersonal account
51 followers25 public repossince Jan 2011Brno University of Technology

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavennet.sf.cssbox:jstyleparser4.0.1-19704 days ago

Metrics by category

Vitality

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

6Critical · 21% of overall
How it's scored
3.6/36Push recency — last push 211 days ago
1.4/36Commit cadence — 2/52 weeks with commits
5.4/18Commit volume — 3 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year3
human_commit_share0.99
days_since_last_push211
active_weeks_last_year2
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

51Moderate · 17% of overall
How it's scored
32.2/60Stars — 97 stars
14.3/25Forks — 53 forks
4.7/15Watchers — 8 watchers
Inputs used
forks53
stars97
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (LGPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

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 factor — 1 contributor(s) cover half of all commits
6/22.5Commit distribution — top contributor authored 73% of commits
13.5/13.5Contributor breadth — 19 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.734
How it's scored
24.7/42Issue resolution — 59% of issues closed
24.6/30PR acceptance — 46/56 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/24 approved changesets -- score normalized to 1
Inputs used
merged_prs46
open_issues31
closed_issues44
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.587
closed_unmerged_prs10
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.3/25Owner reach — 51 followers of radkovo
22.3/25Track record — 25 public repos, account ~15 yr old
Inputs used
followers51
owner_typeUser
is_verified—
owner_loginradkovo
public_repos25
account_age_days5,764
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on maven
14/35Publish recency — latest publish 704 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnet.sf.cssbox:jstyleparser
ecosystemsmaven
any_deprecatedno
min_days_since_publish704

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://cssbox.sourceforge.net/jstyleparser/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttp://cssbox.sourceforge.net/jstyleparser/
docs_sitehttp://cssbox.sourceforge.net/jstyleparser/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 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
0/2.5CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/24 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 10 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Packaging, 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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the maven:net.sf.cssbox:jstyleparser@4.0.1 runtime dependency closure — what installing the published package pulls in — 3 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7/40Legible commit history — 13 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.131
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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.01
How it's scored
45/45Type-checkable code — Java (statically typed)
54.4/55Manageable file sizes — 3/266 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes108,151
source_files_sampled266
oversized_source_files3

Key facts

97GitHub stars
19contributors
3commits, last 12 months
211days since last push
0releases
1bus factor
31open 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 ★ / 53 ⇿
0Stars
53Forks

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.

01020304050605222014-062020-042026-03

Each point covers 11 days.

OpenSSF Scorecard 4.1 / 10
4.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:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/24 approved changesets -- score normalized to 1
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 5
RegistryPackageVersion constraintManifest
Mavenorg.apache.maven.surefire:surefire-junit472.22.2pom.xml
Mavenorg.antlr:antlr4-runtime4.13.2pom.xml
Mavenorg.htmlunit:neko-htmlunit4.7.0pom.xml
Mavenorg.slf4j:slf4j-api1.7.25pom.xml
Mavenorg.unbescape:unbescape1.1.6.RELEASEpom.xml
All dependencies 21

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

RegistryPackageVersionRelation
Mavenorg.antlr:antlr4-runtime4.13.2direct
Mavenorg.apache.maven.surefire:surefire-junit472.22.2direct
Mavenorg.htmlunit:neko-htmlunit4.7.0direct
Mavenorg.slf4j:slf4j-api1.7.25direct
Mavenorg.unbescape:unbescape1.1.6direct
Mavenorg.unbescape:unbescape1.1.6.RELEASEdirect
Mavenjunit:junit4.13.1indirect
Mavenorg.antlr:antlr4-maven-plugin4.13.2indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.13.0indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin—indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin3.0.0-M2indirect
Mavenorg.apache.maven.plugins:maven-gpg-plugin1.6indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.2.0indirect
Mavenorg.apache.maven.plugins:maven-javadoc-plugin3.1.1indirect
Mavenorg.apache.maven.plugins:maven-release-plugin2.5.3indirect
Mavenorg.apache.maven.plugins:maven-resources-plugin3.1.0indirect
Mavenorg.apache.maven.plugins:maven-source-plugin3.1.0indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin2.22.2indirect
Mavenorg.codehaus.mojo:versions-maven-plugin2.7indirect
Mavenorg.hamcrest:hamcrest-core1.3indirect
Mavenorg.sonatype.plugins:nexus-staging-maven-plugin1.6.8indirect
Dependency advisories 0

Installing maven:net.sf.cssbox:jstyleparser@4.0.1 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.