Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 05:29 UTC

FelipeRamosDev / 4hands-api

JavaScriptNo license detected★ 1 star⑂ 0 forkssince Sep 2023View on GitHub ↗

FelipeRamosDev/4hands-api holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on Vitality (66/100) and lowest on Community & Adoption (18/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Felipe RamosPersonal account
16 followers22 public repossince Mar 2019

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
npm4hands-api0.8.6131481 day ago

Metrics by category

Vitality

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

66Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
4.2/36Commit cadence — 6/52 weeks with commits
8.1/18Commit volume — 7 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year7
human_commit_share1
days_since_last_push1
active_weeks_last_year6
How it's scored
27/27Ships releases — 51 releases published
36/36Release recency — latest release 1 days ago
19.8/27Release cadence — a release every ~56 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count51
latest_release_tagv0.8.6
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases56
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?

18Critical · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
0/22.5License — no 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
28.3/80Monthly downloads — 131 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages4hands-api
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads131
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.8/22.5Commit distribution — top contributor authored 96% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.964
How it's scored
0/42Issue resolution — no issues or no data
29.8/30PR acceptance — 293/295 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs293
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.8/25Owner reach — 16 followers of FelipeRamosDev
21.9/25Track record — 22 public repos, account ~7 yr old
Inputs used
followers16
owner_typeUser
is_verified—
owner_loginFelipeRamosDev
public_repos22
account_age_days2,786
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 1 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages4hands-api
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Security

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

23At Risk · 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 28 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/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.2
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.mongodb.com/llms.txt)
40/40Legible commit history — 55 of 59 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.mongodb.com/llms.txt
legible_history_share0.932
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — jsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 59
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsjsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable code — JavaScript with type-check config (jsconfig.json)
55/55Manageable file sizes — 0/149 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes17,509
source_files_sampled149
oversized_source_files0

Key facts

1GitHub stars
2contributors
7commits, last 12 months
1days since last push
51releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-04-16: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 1 stars today.
  • deps.dev does not index npm:4hands-api@0.8.6; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 2.2 / 10
2.2aggregate

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-11-15 05:28 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
npmaxios^1.5.0package.json
npmbcryptjs^3.0.2package.json
npmbinance-sync^0.1.3package.json
npmconnect-redis^7.1.0package.json
npmcors^2.8.5package.json
npmcss-loader^6.8.1package.json
npmcsv-loader^3.0.5package.json
npmdotenv^16.3.1package.json
npmexpress-session^1.17.3package.json
npmexpress-socket.io-session^1.3.5package.json
npmfile-loader^6.2.0package.json
npmhtml-loader^4.2.0package.json
npmioredis^5.4.1package.json
npmjsonwebtoken^9.0.2package.json
npmmongoose^7.5.2package.json
npmnode-schedule^2.1.1package.json
npmnodemailer^6.9.7package.json
npmpath-browserify^1.0.1package.json
npmredis^4.6.10package.json
npmsass^1.67.0package.json
npmsass-loader^13.3.2package.json
npmsocket.io^4.7.2package.json
npmsocket.io-client^4.7.2package.json
npmstyle-loader^3.3.3package.json
npmurl-loader^4.1.1package.json
npmwebpack^5.88.2package.json
npmwebpack-cli^5.1.4package.json
npmwebpack-dev-server^4.15.1package.json
npmxml-loader^1.2.1package.json
npmxml2js^0.6.2package.json
All dependencies 32

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

RegistryPackageVersionRelation
npmaxios^1.5.0direct
npmbcryptjs^3.0.2direct
npmbinance-sync^0.1.3direct
npmconnect-redis^7.1.0direct
npmcors^2.8.5direct
npmcss-loader^6.8.1direct
npmcsv-loader^3.0.5direct
npmdotenv^16.3.1direct
npmexpress-session^1.17.3direct
npmexpress-socket.io-session^1.3.5direct
npmfile-loader^6.2.0direct
npmhtml-loader^4.2.0direct
npmioredis^5.4.1direct
npmjsonwebtoken^9.0.2direct
npmmongoose^7.5.2direct
npmnode-schedule^2.1.1direct
npmnodemailer^6.9.7direct
npmpath-browserify^1.0.1direct
npmredis^4.6.10direct
npmsass^1.67.0direct
npmsass-loader^13.3.2direct
npmsocket.io^4.7.2direct
npmsocket.io-client^4.7.2direct
npmstyle-loader^3.3.3direct
npmurl-loader^4.1.1direct
npmwebpack^5.88.2direct
npmwebpack-cli^5.1.4direct
npmwebpack-dev-server^4.15.1direct
npmxml-loader^1.2.1direct
npmxml2js^0.6.2direct
npmjsdoc^4.0.2indirect
npmnodemon^3.0.1indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — npm.