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

DNSZLSK / muad-dib

Real-time npm/PyPI supply-chain threat detection. Behavioral chain analysis, AST scanning, IOC feeds, and compound scoring engine.

JavaScriptAGPL-3.0★ 15 stars⑂ 7 forkssince Jan 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

DNSZLSK/muad-dib holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Sustainability & Governance (48/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

84
overall / 100
Excellent

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.

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

Ownership

DNSZLSKPersonal account
3 followers15 public repossince Dec 2023

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume2,674 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,674
human_commit_share0.93
days_since_last_push2
active_weeks_last_year30

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 30 days ago
27/27Release cadencea release every ~0.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv2.11.179
releases_from_tagsno
days_since_latest_release30
mean_days_between_releases0.9
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?

50Moderate · 17% of overall
How it's scored
18.6/60Stars15 stars
6.5/25Forks7 forks
0/15Watchers0 watchers
Inputs used
forks7
stars15
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
51.4/80Monthly downloads7,189 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmuaddib-scanner, muaddib-vscode
dependents
ecosystemsnpm
total_downloads
monthly_downloads7,189
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?

48Weak · 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
0/10OpenSSF Scorecard: Contributorsproject 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 resolutionno issues or no data
29.1/30PR acceptance652/673 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/12 approved changesets -- score normalized to 0
Inputs used
merged_prs652
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio
closed_unmerged_prs21
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
4.3/25Owner reach3 followers of DNSZLSK
14.1/25Track record15 public repos, account ~2 yr old
Inputs used
followers3
owner_typeUser
is_verified
owner_loginDNSZLSK
public_repos15
account_age_days967
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on npm
35/35Publish recencylatest publish 30 days ago
20/20Version history428 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmuaddib-scanner, muaddib-vscode
ecosystemsnpm
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/muaddib-scanner
10/10Repository description
10/10Topics15 topics
10/10Wiki
Inputs used
topicsnpm, sarif, security, ast, malware, mitre-attack, scanner, shai-hulud, shai-hulud2, supply-chain, typosquatting, dependency-scanner, pypi, python, supply-chain-security
has_wikiyes
homepagehttps://www.npmjs.com/package/muaddib-scanner
docs_sitehttps://www.npmjs.com/package/muaddib-scanner
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/12 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
3/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: js-yaml 5.2.1 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages31
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:muaddib-scanner@2.11.179 runtime dependency closure — what installing the published package pulls in — 31 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.

71Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, tests/ground-truth/samples/aiconf004-zw-unicode-cursorrules/.cursorrules, tests/samples/red-team-2026/2-promptmink/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history93 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md, tests/ground-truth/samples/aiconf004-zw-unicode-cursorrules/.cursorrules, tests/samples/red-team-2026/2-promptmink/CLAUDE.md
agent_instruction_max_bytes21,259
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance7 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.07
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
52.7/55Manageable file sizes26/619 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes475,421
source_files_sampled619
oversized_source_files26
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessamples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

15GitHub stars
1contributors
2,674commits, last 12 months
2days since last push
100releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
100Releases

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.

1234567712026-042026-062026-08
Major 0Minor 0Patch 100
OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-22 19:13 UTC

9Binary-Artifactsbinaries present in source code
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 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/12 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
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@inquirer/prompts8.5.2package.json
npmacorn8.17.0package.json
npmacorn-walk8.3.5package.json
npmadm-zip0.6.0package.json
npmjs-yaml5.3.0package.json
npmweb-tree-sitter^0.26.9package.json
All dependencies 131

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

RegistryPackageVersionRelation
npm@inquirer/prompts8.5.2direct
npmacorn8.17.0direct
npmacorn-walk8.3.5direct
npmadm-zip0.6.0direct
npmjs-yaml5.3.0direct
npmweb-tree-sitter0.26.11direct
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.6.0indirect
npm@eslint/core1.2.1indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.2indirect
npm@humanfs/core0.19.2indirect
npm@humanfs/node0.16.8indirect
npm@humanfs/types0.15.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@inquirer/ansi2.0.7indirect
npm@inquirer/checkbox5.2.1indirect
npm@inquirer/confirm6.1.1indirect
npm@inquirer/core11.2.1indirect
npm@inquirer/editor5.2.2indirect
npm@inquirer/expand5.1.1indirect
npm@inquirer/external-editor3.0.3indirect
npm@inquirer/figures2.0.7indirect
npm@inquirer/input5.1.2indirect
npm@inquirer/number4.1.1indirect
npm@inquirer/password5.1.1indirect
npm@inquirer/rawlist5.3.1indirect
npm@inquirer/search4.2.1indirect
npm@inquirer/select5.2.1indirect
npm@inquirer/type4.0.7indirect
npm@mapbox/node-pre-gyp^2.0.0indirect
npm@modelcontextprotocol/sdk^1.29.0indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npmacorn-jsx5.3.2indirect
npmajv6.14.0indirect
npmargparse2.0.1indirect
npmaxios^1.10.0indirect
npmaxios^1.6.0indirect
npmaxois^1.0.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.9indirect
npmchalk^5.3.0indirect
npmchardet2.1.1indirect
npmcli-width4.1.0indirect
npmcross-spawn7.0.6indirect
npmcryptokit-env-access^1.0.0indirect
npmcryptokit-logger^1.0.0indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.6.0indirect
npmeslint-plugin-security4.0.1indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmexpres^1.0.0indirect
npmexpress*indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfast-string-truncated-width3.0.3indirect
npmfast-string-width3.0.2indirect
npmfast-wrap-ansi0.2.2indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatmap-stream0.1.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmglobals17.7.0indirect
npmiconv-lite0.7.2indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.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
npmlodahs^1.0.0indirect
npmlodash^4.17.21indirect
npmminimatch10.2.5indirect
npmmodule-to-cdn*indirect
npmmomnet^1.0.0indirect
npmms2.1.3indirect
npmmute-stream3.0.0indirect
npmnatural-compare1.4.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpeacenotwar9.1.3indirect
npmplain-crypto-js*indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmrecat^1.0.0indirect
npmregexp-tree0.1.27indirect
npmrequest^2.88.2indirect
npmsafe-regex2.1.1indirect
npmsafer-buffer2.1.2indirect
npmsecure-chalk^1.0.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmsqlite3*indirect
npmtype-check0.4.0indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
PyPInumpyindirect
PyPIpandasindirect
PyPIrequestsindirect
PyPIscikit-learnindirect
PyPIshapindirect
PyPIxgboostindirect
Dependency advisories 1

Installing npm:muaddib-scanner@2.11.179 pulls in 31 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
js-yaml5.2.1directhigh15.2.2

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.