Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-23 19:08 UTC

mohd-akram / jify

JSON indexed file database/querying library/tool

TypeScriptMIT★ 27 stars⑂ 2 forkssince Sep 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

mohd-akram/jify holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (83/100) and lowest on Vitality (13/100). It was last updated 953 days ago. A single contributor accounts for most of its recent work.

31
overall / 100
At Risk

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.

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

Ownership

Mohamed AkramPersonal account
126 followers78 public repossince Jun 2012Emirates NBD

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
npmjify0.4.03614953 days agojsondatabase

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recencylast push 953 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push953
active_weeks_last_year0
How it's scored
16.2/27Ships releases14 version tags (no GitHub releases)
0/36Release recencylatest release 953 days ago
12.6/27Release cadencea release every ~214.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagv0.4.0
releases_from_tagsyes
days_since_latest_release953
mean_days_between_releases214.6
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?

33At Risk · 17% of overall
How it's scored
23/60Stars27 stars
0/25Forks2 forks
0/15Watchers2 watchers
Inputs used
forks2
stars27
watchers2
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
20.9/80Monthly downloads36 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesjify
dependents
ecosystemsnpm
total_downloads
monthly_downloads36
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?

36Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptance0/4 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs4
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.1/25Owner reach126 followers of mohd-akram
25/25Track record78 public repos, account ~14 yr old
Inputs used
followers126
owner_typeUser
is_verified
owner_loginmohd-akram
public_repos78
account_age_days5,191
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 953 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjify
ecosystemsnpm
any_deprecatedno
min_days_since_publish953

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/jify
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsjson, database, node, nodejs, query, index, npm, nosql
has_wikiyes
homepagehttps://www.npmjs.com/package/jify
docs_sitehttps://www.npmjs.com/package/jify
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 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-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
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 npm:jify@0.4.0 runtime dependency closure — what installing the published package pulls in — 4 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0.6/40Legible commit history1 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.011
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 89
0/8Automated maintenanceno automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/12 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes16,642
source_files_sampled12
oversized_source_files0

Key facts

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

Data collection warnings

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

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks

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.

111222212019-032021-032023-03

Each point covers 4 days.

OpenSSF Scorecard 2.7 / 10
2.7aggregate

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-23 19:08 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities21 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmargparse^2.0.1package.json
npmos-lock^2.0.0package.json
npmtiny-lru^11.2.5package.json
npmz85^0.0.2package.json
All dependencies 161

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

RegistryPackageVersionRelation
npmargparse2.0.1direct
npmos-lock2.0.0direct
npmtiny-lru11.2.5direct
npmz850.0.2direct
npm@aashutoshrathi/word-wrap1.2.6indirect
npm@eslint-community/eslint-utils4.4.0indirect
npm@eslint-community/regexpp4.10.0indirect
npm@eslint/eslintrc2.1.4indirect
npm@eslint/js8.56.0indirect
npm@humanwhocodes/config-array0.11.14indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/object-schema2.0.2indirect
npm@isaacs/cliui8.0.2indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/argparse2.0.14indirect
npm@types/json-schema7.0.15indirect
npm@types/node20.11.0indirect
npm@types/semver7.5.6indirect
npm@typescript-eslint/eslint-plugin6.18.1indirect
npm@typescript-eslint/parser6.18.1indirect
npm@typescript-eslint/scope-manager6.18.1indirect
npm@typescript-eslint/type-utils6.18.1indirect
npm@typescript-eslint/types6.18.1indirect
npm@typescript-eslint/typescript-estree6.18.1indirect
npm@typescript-eslint/utils6.18.1indirect
npm@typescript-eslint/visitor-keys6.18.1indirect
npm@ungap/structured-clone1.2.0indirect
npmacorn8.11.3indirect
npmacorn-jsx5.3.2indirect
npmajv6.12.6indirect
npmansi-regex5.0.1indirect
npmansi-regex6.0.1indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmarray-union2.1.0indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmbrace-expansion2.0.1indirect
npmbraces3.0.2indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolors1.4.0indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.3indirect
npmdebug4.3.4indirect
npmdeep-is0.1.4indirect
npmdir-glob3.0.1indirect
npmdoctrine3.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescape-string-regexp4.0.0indirect
npmeslint8.56.0indirect
npmeslint-scope7.2.2indirect
npmeslint-visitor-keys3.4.3indirect
npmespree9.6.1indirect
npmesquery1.5.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-glob3.3.2indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfastq1.16.0indirect
npmfile-entry-cache6.0.1indirect
npmfill-range7.0.1indirect
npmfind-up5.0.0indirect
npmflat-cache3.2.0indirect
npmflatted3.2.9indirect
npmforeground-child3.1.1indirect
npmfs.realpath1.0.0indirect
npmglob10.3.10indirect
npmglob7.2.3indirect
npmglob-parent5.1.2indirect
npmglob-parent6.0.2indirect
npmglobals13.24.0indirect
npmglobby11.1.0indirect
npmgraphemer1.4.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.0indirect
npmimport-fresh3.3.0indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-docker3.0.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-inside-container1.0.0indirect
npmis-number7.0.0indirect
npmis-path-inside3.0.3indirect
npmis-wsl3.1.0indirect
npmisexe2.0.0indirect
npmjackspeak2.3.6indirect
npmjs-yaml4.1.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash.merge4.6.2indirect
npmlru-cache10.1.0indirect
npmlru-cache6.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.5indirect
npmminimatch3.1.2indirect
npmminimatch9.0.3indirect
npmminipass7.0.4indirect
npmms2.1.2indirect
npmnatural-compare1.4.0indirect
npmonce1.4.0indirect
npmoptionator0.9.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-scurry1.10.1indirect
npmpath-type4.0.0indirect
npmpicomatch2.3.1indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmqueue-microtask1.2.3indirect
npmresolve-from4.0.0indirect
npmreusify1.0.4indirect
npmrimraf3.0.2indirect
npmrun-parallel1.2.0indirect
npmsemver7.5.4indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmslash3.0.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtext-table0.2.0indirect
npmtisk2.0.0indirect
npmto-regex-range5.0.1indirect
npmts-api-utils1.0.3indirect
npmtype-check0.4.0indirect
npmtype-fest0.20.2indirect
npmtypescript5.3.3indirect
npmundici-types5.26.5indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmwrappy1.0.2indirect
npmyallist4.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:jify@0.4.0 pulls in 4 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 statisticsnpm.