Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 04:50 UTC

EryXenX / fca-eryxenx

Modified Facebook Chat API for educational and personal use only. Not affiliated with Meta or Facebook.

JavaScriptMIT★ 2 stars⑂ 3 forkssince Mar 2026View on GitHub ↗

EryXenX/fca-eryxenx holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (68/100) and lowest on Sustainability & Governance (31/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Mohammad Akash Personal account
17 followers5 public repossince Mar 2026

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 publishTags
npmfca-eryxenx37.0.05,438361 day agofacebookchatapimessengerbotunofficialfcafca-eryxenxeryxenx

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
0.7/36Commit cadence — 1/52 weeks with commits
7/18Commit volume — 5 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year5
human_commit_share—
days_since_last_push1
active_weeks_last_year1
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 78 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release78
mean_days_between_releases—
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?

34At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
2.5/25Forks — 3 forks
0/15Watchers — 0 watchers
Inputs used
forks3
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
49.8/80Monthly downloads — 5,438 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfca-eryxenx
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,438
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?

31At Risk · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9/25Owner reach — 17 followers of EryXenX
6.4/25Track record — 5 public repos, account ~0 yr old
Inputs used
followers17
owner_typeUser
is_verified—
owner_loginEryXenX
public_repos5
account_age_days127
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 — 36 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfca-eryxenx
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 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 — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://exxdev.onrender.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://exxdev.onrender.com
docs_sitehttps://exxdev.onrender.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

36Weak · 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 — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/5 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
2/5Security-Policy — security policy file 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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
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_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/145 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes57,403
source_files_sampled145
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — src/api/socket/e2ee/e2ee/proto/ArmadilloApplication.proto, src/api/socket/e2ee/e2ee/proto/ArmadilloICDC.proto, src/api/socket/e2ee/e2ee/proto/ConsumerApplication.proto, src/api/socket/e2ee/e2ee/proto/MessageApplication.proto, src/api/socket/e2ee/e2ee/proto/MessageTransport.proto, src/api/socket/e2ee/e2ee/proto/WACommon.proto, src/api/socket/e2ee/e2ee/proto/WAMediaTransport.proto, src/api/socket/e2ee/e2ee/vendor/proto/ArmadilloApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/ArmadilloICDC.proto, src/api/socket/e2ee/e2ee/vendor/proto/ConsumerApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/MessageApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/MessageTransport.proto, src/api/socket/e2ee/e2ee/vendor/proto/WACommon.proto, src/api/socket/e2ee/e2ee/vendor/proto/WAMediaTransport.proto, src/api/socket/e2ee/proto/ArmadilloApplication.proto, src/api/socket/e2ee/proto/ArmadilloICDC.proto, src/api/socket/e2ee/proto/ConsumerApplication.proto, src/api/socket/e2ee/proto/MessageApplication.proto, src/api/socket/e2ee/proto/MessageTransport.proto, src/api/socket/e2ee/proto/WACommon.proto, src/api/socket/e2ee/proto/WAMediaTransport.proto, src/api/socket/e2ee/vendor/proto/ArmadilloApplication.proto, src/api/socket/e2ee/vendor/proto/ArmadilloICDC.proto, src/api/socket/e2ee/vendor/proto/ConsumerApplication.proto, src/api/socket/e2ee/vendor/proto/MessageApplication.proto, src/api/socket/e2ee/vendor/proto/MessageTransport.proto, src/api/socket/e2ee/vendor/proto/WACommon.proto, src/api/socket/e2ee/vendor/proto/WAMediaTransport.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filessrc/api/socket/e2ee/e2ee/proto/ArmadilloApplication.proto, src/api/socket/e2ee/e2ee/proto/ArmadilloICDC.proto, src/api/socket/e2ee/e2ee/proto/ConsumerApplication.proto, src/api/socket/e2ee/e2ee/proto/MessageApplication.proto, src/api/socket/e2ee/e2ee/proto/MessageTransport.proto, src/api/socket/e2ee/e2ee/proto/WACommon.proto, src/api/socket/e2ee/e2ee/proto/WAMediaTransport.proto, src/api/socket/e2ee/e2ee/vendor/proto/ArmadilloApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/ArmadilloICDC.proto, src/api/socket/e2ee/e2ee/vendor/proto/ConsumerApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/MessageApplication.proto, src/api/socket/e2ee/e2ee/vendor/proto/MessageTransport.proto, src/api/socket/e2ee/e2ee/vendor/proto/WACommon.proto, src/api/socket/e2ee/e2ee/vendor/proto/WAMediaTransport.proto, src/api/socket/e2ee/proto/ArmadilloApplication.proto, src/api/socket/e2ee/proto/ArmadilloICDC.proto, src/api/socket/e2ee/proto/ConsumerApplication.proto, src/api/socket/e2ee/proto/MessageApplication.proto, src/api/socket/e2ee/proto/MessageTransport.proto, src/api/socket/e2ee/proto/WACommon.proto, src/api/socket/e2ee/proto/WAMediaTransport.proto, src/api/socket/e2ee/vendor/proto/ArmadilloApplication.proto, src/api/socket/e2ee/vendor/proto/ArmadilloICDC.proto, src/api/socket/e2ee/vendor/proto/ConsumerApplication.proto, src/api/socket/e2ee/vendor/proto/MessageApplication.proto, src/api/socket/e2ee/vendor/proto/MessageTransport.proto, src/api/socket/e2ee/vendor/proto/WACommon.proto, src/api/socket/e2ee/vendor/proto/WAMediaTransport.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

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

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-07-15 04:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/5 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file 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
0SASTno SAST tool detected
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
npmaxios^1.13.5package.json
npmaxios-cookiejar-support^5.0.5package.json
npmbluebird^3.7.2package.json
npmchalk^4.1.2package.json
npmcheerio1.0.0-rc.12package.json
npmduplexify^4.1.3package.json
npmgradient-string^2.0.2package.json
npmhttps-proxy-agent^4.0.0package.json
npmmqtt^5.10.1package.json
npmsequelize^6.37.6package.json
npmsqlite3^5.1.7package.json
npmtotp-generator^1.0.0package.json
npmws^8.18.0package.json
npm@noble/curves^2.2.0package.json
npm@noble/hashes^2.2.0package.json
npm@signalapp/libsignal-client0.70.0package.json
npmmime^3.0.0package.json
npmprotobufjs^8.4.0package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.