jaystack / odata-v4-mongodb
This server component lets you process OData requests over a MongoDB database
jaystack/odata-v4-mongodb holds a health index of 25 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (51/100) and lowest on Vitality (1/100). It was last updated 837 days ago. A single contributor accounts for most of its recent work.
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.
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 31 is calibrated to 25 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | odata-v4-mongodb | 0.1.12 | 4,455 | 17 | 3306 days ago | odataserverv4parser |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 0/36 | Push recency — last push 837 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — no data |
Inputs used
| commits_last_year | 0 |
| human_commit_share | 1 |
| days_since_last_push | 837 |
| active_weeks_last_year | 0 |
Release discipline
How it's scored
| 0/27 | Ships releases — no releases published |
| 0/36 | Release recency — no releases |
| 0/27 | Release cadence — no releases |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 0 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 24/60 | Stars — 31 stars |
| 11.3/25 | Forks — 24 forks |
| 5.6/15 | Watchers — 11 watchers |
Inputs used
| forks | 24 |
| stars | 31 |
| watchers | 11 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 0/22.5 | License — no license file detected |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | 0 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
How it's scored
| 48.7/80 | Monthly downloads — 4,455 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | odata-v4-mongodb |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 4,455 |
| unverified_packages_excluded | — |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 10.2/22.5 | Commit distribution — top contributor authored 55% of commits |
| 8.1/13.5 | Contributor breadth — 6 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — no data |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 6 |
| top_contributor_share | 0.545 |
Issue & PR responsiveness
How it's scored
| 31.5/42 | Issue resolution — 75% of issues closed |
| 4.3/30 | PR acceptance — 1/7 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — no data |
Inputs used
| merged_prs | 1 |
| open_issues | 3 |
| closed_issues | 9 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 0.75 |
| closed_unmerged_prs | 6 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 7.8/25 | Owner reach — 11 followers of jaystack |
| 25/25 | Track record — 106 public repos, account ~13 yr old |
Inputs used
| followers | 11 |
| owner_type | Organization |
| is_verified | no |
| owner_login | jaystack |
| public_repos | 106 |
| account_age_days | 5,109 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on npm |
| 4/35 | Publish recency — latest publish 3,306 days ago |
| 20/20 | Version history — 17 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | odata-v4-mongodb |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 3,306 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 0/30 | Security policy (SECURITY.md) |
| 0/25 | Dependabot config |
| 0/25 | Dependency lockfiles — published library — lockfiles are an application concern, not expected |
| 0/20 | CodeQL workflow |
Inputs used
| source | file_signals |
| lockfiles | — |
| manifests | package.json |
| has_codeql_workflow | no |
| has_security_policy | no |
| has_dependabot_config | no |
Dependency advisories
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 2 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 4.8/40 | Legible commit history — 2 of 22 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.091 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — tsconfig.json |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 22 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 55/55 | Manageable file sizes — 0/4 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 8,567 |
| source_files_sampled | 4 |
| oversized_source_files | 0 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/jaystack/odata-v4-mongodb: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-10T14:50:11Z. Please include `DE58:921AB:BDC4989:B84E299:6AA2C3A0` when reporting this issue.); skipping Scorecard checks
More detail
Star and fork history 0 ★ / 24 ⇿
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.
Each point covers 9 days.
Direct dependencies 2
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | odata-v4-literal | ^0.1.0 | package.json |
| npm | odata-v4-parser | ^0.1.18 | package.json |
All dependencies 6
Full resolved dependency set from the GitHub dependency graph: 2 direct and 4 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | odata-v4-literal | ^0.1.0 | direct |
| npm | odata-v4-parser | ^0.1.18 | direct |
| npm | chai | ^3.5.0 | indirect |
| npm | mocha | ^3.2.0 | indirect |
| npm | mocha-junit-reporter | ^1.13.0 | indirect |
| npm | typescript | ^2.2.1 | indirect |
Dependency advisories 0
Installing npm:odata-v4-mongodb@0.1.12 pulls in 2 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.
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.