Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 16:21 UTC

mintlify / config

JavaScriptNo license detected★ 4 stars⑂ 5 forkssince Feb 2023View on GitHub ↗
KindLibraryhow this is determined

mintlify/config holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (76/100) and lowest on Vitality (7/100). It was last updated 238 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

MintlifyOrganization · verified domain
1,705 followers39 public repossince Oct 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@mintlify/ts-config2.0.225,064131042 days ago—
npm@mintlify/oxfmt-config1.0.0121283 days agooxfmtformatterconfig
npm@mintlify/eslint-config1.0.67937686 days ago—
npm@mintlify/oxlint-config1.0.2153283 days agooxlintconfig
npm@mintlify/prettier-config1.0.65,8777887 days ago—
npm@mintlify/eslint-config-next1.0.187119686 days ago—
npm@mintlify/eslint-config-typescript1.0.1346814686 days ago—
npm@mintlify/eslint-config-typescript-react1.0.2193686 days ago—

Metrics by category

Vitality

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

7Critical · 21% of overall

Development activity

11Critical
How it's scored
3.6/36Push recency — last push 238 days ago
1.4/36Commit cadence — 2/52 weeks with commits
6.3/18Commit volume — 4 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share1
days_since_last_push238
active_weeks_last_year2

Release discipline

1Critical
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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

Popularity & adoption

15Critical
How it's scored
7.7/60Stars — 4 stars
5/25Forks — 5 forks
2.7/15Watchers — 4 watchers
Inputs used
forks5
stars4
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

Community health

25At Risk
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

Ecosystem adoption (downloads)

75Good
How it's scored
60.1/80Monthly downloads — 32,319 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@mintlify/ts-config, @mintlify/oxfmt-config, @mintlify/eslint-config, @mintlify/oxlint-config, @mintlify/prettier-config, @mintlify/eslint-config-next, @mintlify/eslint-config-typescript, @mintlify/eslint-config-typescript-react
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads32,319
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?

76Good · 23% of overall

Maintainer resilience (bus factor)

50Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.5/22.5Commit distribution — top contributor authored 40% of commits
8.1/13.5Contributor breadth — 6 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.4

Issue & PR responsiveness

75Good
How it's scored
0/42Issue resolution — no issues or no data
24.9/30PR acceptance — 29/35 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 20/30 approved changesets -- score normalized to 6
Inputs used
merged_prs29
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs6
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.

Ownership & stewardship

95Exceptional
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
23.2/25Owner reach — 1,705 followers of mintlify
21.4/25Track record — 39 public repos, account ~4 yr old
Inputs used
followers1,705
owner_typeOrganization
is_verifiedyes
owner_loginmintlify
public_repos39
account_age_days1,785

Package maintenance

91Excellent
How it's scored
25/25Published & resolvable — 8 package(s) on npm
26/35Publish recency — latest publish 283 days ago
20/20Version history — 19 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@mintlify/ts-config, @mintlify/oxfmt-config, @mintlify/eslint-config, @mintlify/oxlint-config, @mintlify/prettier-config, @mintlify/eslint-config-next, @mintlify/eslint-config-typescript, @mintlify/eslint-config-typescript-react
ecosystemsnpm
any_deprecatedno
min_days_since_publish283

Engineering Quality

Are baseline engineering and documentation practices in place?

22At Risk · 19% of overall

Engineering practices

6Critical
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 29 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

45Weak
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://mintlify.com/
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://mintlify.com/
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

34At Risk · 16% of overall

Security posture

34At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 29 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
4.5/7.5Code-Review — Found 20/30 approved changesets -- score normalized to 6
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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_aggregate3.4
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.

34At Risk · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 29 of 30 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.967
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

12Critical
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/ts-config/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 30
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/ts-config/tsconfig.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.

Code legibility for models

82Excellent
How it's scored
27/45Type-checkable code — JavaScript with type-check config (packages/ts-config/tsconfig.json)
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes761
source_files_sampled5
oversized_source_files0

Key facts

4GitHub stars
6contributors
4commits, last 12 months
238days since last push
0releases
2bus 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 2023-06-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 4 stars today.
  • Could not fetch npm package '@mintlify/config' from its registry
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 4 ★ / 5 ⇿
4Stars
5Forks

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.

Star history is shown as collected on 2023-06-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

123454532023-022024-102026-06

Each point covers 4 days.

OpenSSF Scorecard 3.4 / 10
3.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-12 16:21 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 29 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 20/30 approved changesets -- score normalized to 6
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 11
RegistryPackageVersion constraintManifest
npm@mintlify/eslint-config-typescript^1.0.13packages/eslint-config-next/package.json
npmeslint-config-next13.xpackages/eslint-config-next/package.json
npm@mintlify/eslint-config-typescript^1.0.13packages/eslint-config-typescript-react/package.json
npmeslint-plugin-react7.xpackages/eslint-config-typescript-react/package.json
npmeslint-plugin-react-hooks4.xpackages/eslint-config-typescript-react/package.json
npmeslint-plugin-jsx-a11y6.xpackages/eslint-config-typescript-react/package.json
npm@mintlify/eslint-config^1.0.6packages/eslint-config-typescript/package.json
npm@typescript-eslint/eslint-plugin6.xpackages/eslint-config-typescript/package.json
npmeslint-plugin-import2.xpackages/eslint-config-typescript/package.json
npmeslint-config-prettier9.xpackages/eslint-config/package.json
npmeslint-plugin-unused-imports3.xpackages/eslint-config/package.json
All dependencies 10

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

RegistryPackageVersionRelation
npm@mintlify/eslint-config^1.0.6direct
npm@mintlify/eslint-config-typescript^1.0.13direct
npm@typescript-eslint/eslint-plugin6.xdirect
npmeslint-config-next13.xdirect
npmeslint-config-prettier9.xdirect
npmeslint-plugin-import2.xdirect
npmeslint-plugin-jsx-a11y6.xdirect
npmeslint-plugin-react7.xdirect
npmeslint-plugin-react-hooks4.xdirect
npmeslint-plugin-unused-imports3.xdirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with mintlify/config. Read them side by side →

86anolilab/javascript-style-guideThis project is a code style guide of all basic back- and front end project used at Anolilab.Excellent84alleyinteractive/alley-scriptsA collection of scripts and utilities for Alley projects.Excellent98appium/appiumCross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocolExceptional97vitejs/devtoolsDevTools Framework for the Vite Ecosystem. Exceptional90ofri-peretz/eslintSecurity and code-quality ESLint plugins — 477 rules across 30 packages: 272 security rules mapped to CWE + OWASP, 107 quality, 98 React/a11y. ESLint 8.40/9/10 + Oxlint. The lint layer AI-generated code needs.Excellent89lint-staged/lint-staged🚫💩 — Run tasks like formatters and linters against staged git filesExcellent

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.