Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 20:15 UTC

zakariagharzouli / sparda

AI writes. SPARDA proves. A deterministic, offline gate that catches when an AI edit removes a guard, exposes a route, or breaks an invariant — no API key, right in the agent edit loop.

JavaScriptCustom license★ 8 stars⑂ 1 forksince Jun 2026View on GitHub ↗
KindLibraryCommand-line toolMCP serverNetwork servicehow this is determined

zakariagharzouli/sparda holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Sustainability & Governance (38/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

gharzouli zakaria Personal account
1 follower29 public repossince Jan 2025RESIDUAL LABS

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?

76Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
6.2/36Commit cadence — 9/52 weeks with commits
18/18Commit volume — 109 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year109
human_commit_share1
days_since_last_push3
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 8 releases published
36/36Release recency — latest release 44 days ago
27/27Release cadence — a release every ~4.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count8
latest_release_tagv0.68.0
releases_from_tagsno
days_since_latest_release44
mean_days_between_releases4.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?

47Weak · 17% of overall
How it's scored
13.7/60Stars — 8 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars8
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
43.3/80Monthly downloads — 1,753 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessparda-mcp
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,753
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?

38Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.972
How it's scored
0/42Issue resolution — 0% of issues closed
16.2/30PR acceptance — 14/26 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs14
open_issues1
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0
closed_unmerged_prs12
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
2.2/25Owner reach — 1 followers of zakariagharzouli
14.1/25Track record — 29 public repos, account ~1 yr old
Inputs used
followers1
owner_typeUser
is_verified—
owner_loginzakariagharzouli
public_repos29
account_age_days614
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 3 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessparda-mcp
ecosystemsnpm
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 3 out of 3 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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsai-agents, ai-code-review, authorization, bola, claude-code, guardrails, mcp, security, static-analysis, trust-layer
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 3 out of 3 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/28 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
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
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 29 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages118
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:sparda-mcp@0.72.1 runtime dependency closure — what installing the published package pulls in — 118 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.

60Moderate · 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 — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.95
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tests/fixtures/nest-class-seeding/tsconfig.json, tests/fixtures/nest-di-blindspot-location/tsconfig.json, tests/fixtures/nest-direct-provider/tsconfig.json, tests/fixtures/nest-provider-tapp/tsconfig.json, tests/fixtures/nest-strict-chain/tsconfig.json, tests/fixtures/ubg-graphql-resolver/tsconfig.json, tests/fixtures/ubg-guard-dominance/tsconfig.json, tests/fixtures/ubg-nest-all-verb/tsconfig.json, tests/fixtures/ubg-nest-passport/tsconfig.json, tests/fixtures/ubg-nest-status-const/tsconfig.json, tests/fixtures/ubg-nestjs-deep/tsconfig.json, tests/fixtures/ubg-nextjs-hoc-guard/tsconfig.json, tests/fixtures/ubg-param-auth-decorator/tsconfig.json, tests/fixtures/ubg-server-actions/tsconfig.json
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
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_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstests/fixtures/nest-class-seeding/tsconfig.json, tests/fixtures/nest-di-blindspot-location/tsconfig.json, tests/fixtures/nest-direct-provider/tsconfig.json, tests/fixtures/nest-provider-tapp/tsconfig.json, tests/fixtures/nest-strict-chain/tsconfig.json, tests/fixtures/ubg-graphql-resolver/tsconfig.json, tests/fixtures/ubg-guard-dominance/tsconfig.json, tests/fixtures/ubg-nest-all-verb/tsconfig.json, tests/fixtures/ubg-nest-passport/tsconfig.json, tests/fixtures/ubg-nest-status-const/tsconfig.json, tests/fixtures/ubg-nestjs-deep/tsconfig.json, tests/fixtures/ubg-nextjs-hoc-guard/tsconfig.json, tests/fixtures/ubg-param-auth-decorator/tsconfig.json, tests/fixtures/ubg-server-actions/tsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tests/fixtures/nest-class-seeding/tsconfig.json, tests/fixtures/nest-di-blindspot-location/tsconfig.json, tests/fixtures/nest-direct-provider/tsconfig.json, tests/fixtures/nest-provider-tapp/tsconfig.json, tests/fixtures/nest-strict-chain/tsconfig.json, tests/fixtures/ubg-graphql-resolver/tsconfig.json, tests/fixtures/ubg-guard-dominance/tsconfig.json, tests/fixtures/ubg-nest-all-verb/tsconfig.json, tests/fixtures/ubg-nest-passport/tsconfig.json, tests/fixtures/ubg-nest-status-const/tsconfig.json, tests/fixtures/ubg-nestjs-deep/tsconfig.json, tests/fixtures/ubg-nextjs-hoc-guard/tsconfig.json, tests/fixtures/ubg-param-auth-decorator/tsconfig.json, tests/fixtures/ubg-server-actions/tsconfig.json)
54.5/55Manageable file sizes — 8/942 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes173,144
source_files_sampled942
oversized_source_files8
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — tests/fixtures/ubg-openapi-ghost/openapi.json, tests/fixtures/ubg-openapi/openapi.json
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_filestests/fixtures/ubg-openapi-ghost/openapi.json, tests/fixtures/ubg-openapi/openapi.json
interfaces_expected_ofnetwork-service

Key facts

8GitHub stars
2contributors
109commits, last 12 months
3days since last push
8releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'demo-crm' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-08 20:14 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests3 out of 3 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/28 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
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
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities29 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npmexpress^4.19.0demo-app/package.json
npm@babel/parser8.0.4package.json
npm@babel/traverse8.0.4package.json
npm@clack/prompts1.7.0package.json
npm@modelcontextprotocol/sdk1.29.0package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:sparda-mcp@0.72.1 pulls in 118 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 statistics — npm.