Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 15:32 UTC

dazl-dev / resolve-directory-context

Helpers to get information about single/multi-package contexts.

TypeScriptMIT★ 2 stars⑂ 2 forkssince Aug 2021View on GitHub ↗

dazl-dev/resolve-directory-context holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Engineering Quality (64/100) and lowest on Community & Adoption (36/100). It was last updated 33 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

dazl.devOrganization
5 followers14 public repossince Aug 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@dazl/resolve-directory-context5.1.024,0962432 days agopackagesdirectoryworkspacenpmyarn

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
18/36Push recency — last push 33 days ago
22.2/36Commit cadence — 32/52 weeks with commits
17.9/18Commit volume — 97 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_year97
human_commit_share0.58
days_since_last_push33
active_weeks_last_year32
How it's scored
27/27Ships releases — 15 releases published
7.2/36Release recency — latest release 432 days ago
12.6/27Release cadence — a release every ~135.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count15
latest_release_tagv5.1.0
releases_from_tagsno
days_since_latest_release432
mean_days_between_releases135.5
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?

36Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io
has_pull_request_templateno
How it's scored
58.4/80Monthly downloads — 24,096 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@dazl/resolve-directory-context
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads24,096
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?

42Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.988
How it's scored
0/42Issue resolution — no issues or no data
21.9/30PR acceptance — 441/603 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/21 approved changesets -- score normalized to 0
Inputs used
merged_prs441
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs162
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
30/30Ownership backing — organization-owned
0/20Verified domain
5.6/25Owner reach — 5 followers of dazl-dev
11.2/25Track record — 14 public repos, account ~1 yr old
Inputs used
followers5
owner_typeOrganization
is_verifiedno
owner_logindazl-dev
public_repos14
account_age_days474
How it's scored
25/25Published & resolvable — 1 package(s) on npm
14/35Publish recency — latest publish 432 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@dazl/resolve-directory-context
ecosystemsnpm
any_deprecatedno
min_days_since_publish432

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 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
2.5/2.5CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/21 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
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file 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
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
20.2/35Direct dependencies free of known advisories — 1 affected: minimatch 10.2.6 (moderate 5.3)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages5
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages1
Matched the npm:@dazl/resolve-directory-context@5.1.0 runtime dependency closure — what installing the published package pulls in — 5 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 58 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
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 — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 42 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.42
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/12 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes4,441
source_files_sampled12
oversized_source_files0

Key facts

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

Data collection warnings

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

More detail

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-11-21 15:32 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/21 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmminimatch^10.2.6package.json
npmtype-fest^5.8.0package.json
All dependencies 149

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

RegistryPackageVersionRelation
npmminimatch10.2.6direct
npmtype-fest5.8.0direct
npm@esbuild/aix-ppc640.28.1indirect
npm@esbuild/android-arm0.28.1indirect
npm@esbuild/android-arm640.28.1indirect
npm@esbuild/android-x640.28.1indirect
npm@esbuild/darwin-arm640.28.1indirect
npm@esbuild/darwin-x640.28.1indirect
npm@esbuild/freebsd-arm640.28.1indirect
npm@esbuild/freebsd-x640.28.1indirect
npm@esbuild/linux-arm0.28.1indirect
npm@esbuild/linux-arm640.28.1indirect
npm@esbuild/linux-ia320.28.1indirect
npm@esbuild/linux-loong640.28.1indirect
npm@esbuild/linux-mips64el0.28.1indirect
npm@esbuild/linux-ppc640.28.1indirect
npm@esbuild/linux-riscv640.28.1indirect
npm@esbuild/linux-s390x0.28.1indirect
npm@esbuild/linux-x640.28.1indirect
npm@esbuild/netbsd-arm640.28.1indirect
npm@esbuild/netbsd-x640.28.1indirect
npm@esbuild/openbsd-arm640.28.1indirect
npm@esbuild/openbsd-x640.28.1indirect
npm@esbuild/openharmony-arm640.28.1indirect
npm@esbuild/sunos-x640.28.1indirect
npm@esbuild/win32-arm640.28.1indirect
npm@esbuild/win32-ia320.28.1indirect
npm@esbuild/win32-x640.28.1indirect
npm@file-services/memory11.1.1indirect
npm@file-services/path11.1.1indirect
npm@file-services/types11.1.1indirect
npm@file-services/utils11.1.1indirect
npm@playwright/browser-chromium1.62.0indirect
npm@ts-tools/esm7.0.0indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/mocha10.0.10indirect
npm@types/node22.20.1indirect
npmaccepts2.0.0indirect
npmargparse2.0.1indirect
npmassertion-error2.0.1indirect
npmbalanced-match4.0.4indirect
npmbody-parser2.3.0indirect
npmbrace-expansion5.0.8indirect
npmbrowser-stdout1.3.1indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmchai6.2.2indirect
npmchokidar5.0.0indirect
npmcommander15.0.0indirect
npmcontent-disposition1.1.0indirect
npmcontent-type1.0.5indirect
npmcontent-type2.0.0indirect
npmcookie0.7.2indirect
npmcookie-signature1.2.2indirect
npmcreate-listening-server2.1.0indirect
npmdebug4.4.3indirect
npmdepd2.0.0indirect
npmdiff9.0.0indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmesbuild0.28.1indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmexpress5.2.1indirect
npmfinalhandler2.1.1indirect
npmfind-up5.0.0indirect
npmfind-up8.0.0indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob13.0.6indirect
npmgopd1.2.0indirect
npmhas-flag4.0.0indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.4indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.7.3indirect
npminherits2.0.4indirect
npmipaddr.js1.9.1indirect
npmis-path-inside3.0.3indirect
npmis-promise4.0.0indirect
npmis-unicode-supported0.1.0indirect
npmjs-yaml5.2.2indirect
npmlocate-path6.0.0indirect
npmlocate-path8.0.0indirect
npmlru-cache11.5.2indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.1indirect
npmmerge-descriptors2.0.0indirect
npmmime4.1.0indirect
npmmime-db1.54.0indirect
npmmime-types3.0.2indirect
npmminipass7.1.3indirect
npmmocha12.0.0-rc.5indirect
npmmocha-web3.0.0indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-limit4.0.0indirect
npmp-locate5.0.0indirect
npmp-locate6.0.0indirect
npmparseurl1.3.3indirect
npmpath-exists4.0.0indirect
npmpath-scurry2.0.2indirect
npmpath-to-regexp8.4.2indirect
npmpicocolors1.1.1indirect
npmplaywright-core1.62.0indirect
npmprettier3.9.6indirect
npmproxy-addr2.0.7indirect
npmqs6.15.3indirect
npmrange-parser1.3.0indirect
npmraw-body3.0.2indirect
npmreaddirp5.0.0indirect
npmrouter2.2.0indirect
npmsafer-buffer2.1.2indirect
npmsend1.2.1indirect
npmserialize-javascript7.0.7indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmside-channel1.1.1indirect
npmside-channel-list1.0.1indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstatuses2.0.2indirect
npmstrip-json-comments5.0.3indirect
npmsupports-color8.1.1indirect
npmtagged-tag1.0.0indirect
npmtoidentifier1.0.1indirect
npmtype-is2.1.0indirect
npmtypescript6.0.3indirect
npmundici-types6.21.0indirect
npmunicorn-magic0.3.0indirect
npmunpipe1.0.0indirect
npmvary1.1.2indirect
npmworkerpool10.0.3indirect
npmwrappy1.0.2indirect
npmyocto-queue0.1.0indirect
npmyocto-queue1.2.2indirect
Dependency advisories 1

Installing npm:@dazl/resolve-directory-context@5.1.0 pulls in 5 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
minimatch10.2.6directmoderate111.0.1

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