Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 21:57 UTC

viniciussanchez / RESTRequest4Delphi

API to consume REST services written in any programming language with support to Lazarus and Delphi

PascalMIT★ 621 stars⑂ 180 forkssince Jul 2019View on GitHub ↗

viniciussanchez/RESTRequest4Delphi holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (84/100) and lowest on Engineering Quality (48/100). It was last updated 1 day 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

Vinicius SanchezPersonal account
788 followers24 public repossince Dec 2015BDMG

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

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
15.9/36Commit cadence23/52 weeks with commits
17.5/18Commit volume88 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year88
human_commit_share0.85
days_since_last_push1
active_weeks_last_year23
How it's scored
27/27Ships releases78 releases published
36/36Release recencylatest release 28 days ago
19.8/27Release cadencea release every ~52.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count78
latest_release_tagv4.0.32
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases52.1
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?

62Moderate · 17% of overall
How it's scored
45.3/60Stars621 stars
18.8/25Forks180 forks
9.2/15Watchers47 watchers
Inputs used
forks180
stars621
watchers47
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesopencollective.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.1/22.5Commit distributiontop contributor authored 68% of commits
13.5/13.5Contributor breadth41 contributors
10/10OpenSSF Scorecard: Contributorsproject has 19 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled41
top_contributor_share0.683
How it's scored
42/42Issue resolution100% of issues closed
25.9/30PR acceptance119/138 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 6/9 approved changesets -- score normalized to 6
Inputs used
merged_prs119
open_issues0
closed_issues82
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs19
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.8/25Owner reach788 followers of viniciussanchez
22.2/25Track record24 public repos, account ~10 yr old
Inputs used
followers788
owner_typeUser
is_verified
owner_loginviniciussanchez
public_repos24
account_age_days3,910
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://go.hotmart.com/U88695509H
10/10Repository description
10/10Topics12 topics
10/10Wiki
Inputs used
topicsrest, request, client, api, delphi, simple, lazarus, fpc, embarcadero, indy, nethttp, freepascal
has_wikiyes
homepagehttps://go.hotmart.com/U88695509H
docs_sitehttps://go.hotmart.com/U88695509H
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

63Moderate · 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
0/2.5CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 6/9 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 19 contributing companies or organizations
0/10Dangerous-Workflowno data
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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages97
unassessed_packages0
affected_by_severitymoderate 1
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 97 resolved dependencies against OSV. 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.7/40Legible commit history49 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.576
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance15 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.15
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePascal without a type-check config
55/55Manageable file sizes0/1 source files over 60KB
Inputs used
primary_languagePascal
largest_source_bytes2,076
source_files_sampled1
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 examplessamples
Inputs used
example_dirssamples
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

621GitHub stars
41contributors
88commits, last 12 months
1days since last push
78releases
1bus factor
0open issues
package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 180 ⇿
0Stars
180Forks
78Releases

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.

0408012016020017842019-072023-012026-08
Major 4Minor 4Patch 70

Each point covers 7 days.

OpenSSF Scorecard 5.4 / 10
5.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-09-04 21:57 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 6/9 approved changesets -- score normalized to 6
10Contributorsproject has 19 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
8Vulnerabilities2 existing vulnerabilities detected
All dependencies 97

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

RegistryPackageVersionRelation
npmabbrev1.1.1indirect
npmaccepts2.0.0indirect
npmanymatch3.1.2indirect
npmbalanced-match4.0.4indirect
npmbinary-extensions2.2.0indirect
npmbody-parser2.3.0indirect
npmbrace-expansion5.0.9indirect
npmbraces3.0.3indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmchokidar3.5.3indirect
npmcontent-disposition1.1.0indirect
npmcontent-type1.0.5indirect
npmcontent-type2.1.0indirect
npmcookie0.7.1indirect
npmcookie-signature1.2.2indirect
npmcors2.8.5indirect
npmdebug4.4.3indirect
npmdepd2.0.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmexpress5.2.1indirect
npmfill-range7.1.1indirect
npmfinalhandler2.1.1indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfsevents2.3.2indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob-parent5.1.2indirect
npmgopd1.2.0indirect
npmhas-flag3.0.0indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.2indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.7.3indirect
npmignore-by-default1.0.1indirect
npminherits2.0.4indirect
npmipaddr.js1.9.1indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-promise4.0.0indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.1indirect
npmmerge-descriptors2.0.0indirect
npmmime-db1.54.0indirect
npmmime-types3.0.2indirect
npmminimatch10.2.4indirect
npmms2.1.3indirect
npmnegotiator1.1.0indirect
npmnodemon3.1.14indirect
npmnopt1.0.10indirect
npmnormalize-path3.0.0indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmparseurl1.3.3indirect
npmpath-to-regexp8.4.2indirect
npmpicomatch2.3.2indirect
npmproxy-addr2.0.7indirect
npmpstree.remy1.1.8indirect
npmqs6.15.2indirect
npmrange-parser1.3.0indirect
npmraw-body3.0.2indirect
npmreaddirp3.6.0indirect
npmrouter2.2.0indirect
npmsafer-buffer2.1.2indirect
npmsemver7.7.4indirect
npmsend1.2.1indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmside-channel1.1.0indirect
npmside-channel-list1.0.0indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmsimple-update-notifier2.0.0indirect
npmstatuses2.0.2indirect
npmsupports-color5.5.0indirect
npmto-regex-range5.0.1indirect
npmtoidentifier1.0.1indirect
npmtouch3.1.0indirect
npmtype-is2.1.0indirect
npmundefsafe2.0.5indirect
npmunpipe1.0.0indirect
npmvary1.1.2indirect
npmwrappy1.0.2indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 97 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
qs6.15.2indirectmoderate26.16.0

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.