Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 17:58 UTC

Trusty-Squire / trusty-squire

Trusty Squire signs up / in to websites for you so you don’t have to.

TypeScriptMIT★ 3 stars⑂ 1 forksince May 2026View on GitHub ↗
KindWeb interfaceNetwork serviceMCP serverCommand-line toolLibraryhow this is determined
#api-keys#browser-automation#coding-agents#mcp#model-context-protocol#secrets-management#website-login#website-signup

Trusty-Squire/trusty-squire holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (94/100) and lowest on Community & Adoption (37/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

Trusty SquireOrganization
0 followers3 public repossince May 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@trusty-squire/mcp1.1.1513,2234200 days agomcpmodel-context-protocolai-agentcoding-agentbrowser-automationwebsite-signupwebsite-loginsaasapi-keyssecrets-managementclaude-codecursorcodexopencode
npm@trusty-squire/skill-schema0.1.62,2741330 days agotrusty-squireskillschemazod
npm@trusty-squire/recipe-schema0.1.01,812530 days agotrusty-squireoperator-recipeschemazod

Metrics by category

Vitality

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

82Excellent · 21% of overall

Development activity

77Good
How it's scored
36/36Push recency — last push 0 days ago
13.2/36Commit cadence — 19/52 weeks with commits
18/18Commit volume — 2,034 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,034
human_commit_share1
days_since_last_push0
active_weeks_last_year19

Release discipline

90Excellent
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~0.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv1.1.16-rc.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

37Weak · 17% of overall

Popularity & adoption

5Critical
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

71Good
How it's scored
56.5/80Monthly downloads — 17,309 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@trusty-squire/mcp, @trusty-squire/skill-schema, @trusty-squire/recipe-schema
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads17,309
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?

53Moderate · 23% of overall

Maintainer resilience (bus factor)

13Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

80Excellent
How it's scored
40/42Issue resolution — 95% of issues closed
29.2/30PR acceptance — 701/719 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs701
open_issues6
closed_issues122
prs_merged_7d60
prs_decided_7d60
prs_merged_30d60
prs_decided_30d60
issue_closed_ratio0.953
closed_unmerged_prs18
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.

Ownership & stewardship

35Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of Trusty-Squire
5.1/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginTrusty-Squire
public_repos3
account_age_days130

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on npm
35/35Publish recency — latest publish 0 days ago
20/20Version history — 420 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@trusty-squire/mcp, @trusty-squire/skill-schema, @trusty-squire/recipe-schema
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

94Exceptional · 19% of overall

Engineering practices

90Excellent
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://trustysquire.ai
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsapi-keys, browser-automation, coding-agents, mcp, model-context-protocol, secrets-management, website-login, website-signup
has_wikiyes
homepage—
docs_sitehttps://trustysquire.ai
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

49Weak · 16% of overall

Security posture

42Weak
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 — 30 out of 30 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/30 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
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 72 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

76Good
How it's scored
11.5/35Direct dependencies free of known advisories — 1 affected: sharp 0.34.5 (high 8.4)
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
advisories2
affected_packages1
assessed_packages279
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:@trusty-squire/mcp@1.1.15 runtime dependency closure — what installing the published package pulls in — 279 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.

67Good · 4% of overall

Agent context & guidance

85Excellent
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, apps/web/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md, apps/web/AGENTS.md
agent_instruction_max_bytes69,220

Verify loop (build / test / typecheck)

58Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — apps/api/tsconfig.json, apps/mcp/tsconfig.json, apps/registry/tsconfig.json, apps/web/tsconfig.json, packages/recipe-schema/tsconfig.json, packages/skill-schema/tsconfig.json, packages/vault/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsapps/api/tsconfig.json, apps/mcp/tsconfig.json, apps/registry/tsconfig.json, apps/web/tsconfig.json, packages/recipe-schema/tsconfig.json, packages/skill-schema/tsconfig.json, packages/vault/tsconfig.json
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.6/55Manageable file sizes — 16/635 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes336,675
source_files_sampled635
oversized_source_files16

Machine-readable interfaces

20At Risk
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

3GitHub stars
1contributors
2,034commits, last 12 months
0days since last push
100releases
1bus factor
6open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-18 17:58 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-Tests30 out of 30 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/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities72 existing vulnerabilities detected
Direct dependencies 55
RegistryPackageVersion constraintManifest
npm@fastify/cookie^9.4.0apps/api/package.json
npm@fastify/rate-limit^9.1.0apps/api/package.json
npm@prisma/client^5.22.0apps/api/package.json
npm@trusty-squire/skill-schemaworkspace:*apps/api/package.json
npm@trusty-squire/vaultworkspace:*apps/api/package.json
npmbullmq^5.21.1apps/api/package.json
npmcanonicalize^2.0.0apps/api/package.json
npmfastify^4.28.0apps/api/package.json
npmimapflow^1.3.3apps/api/package.json
npmjose^5.9.6apps/api/package.json
npmnodemailer^8.0.7apps/api/package.json
npmpino^9.5.0apps/api/package.json
npmstripe^22.2.0apps/api/package.json
npmulid^2.3.0apps/api/package.json
npmzod^3.23.8apps/api/package.json
npm@anthropic-ai/sdk^0.32.1apps/mcp/package.json
npm@clack/prompts^0.11.0apps/mcp/package.json
npm@hpke/core^1.9.0apps/mcp/package.json
npm@modelcontextprotocol/sdk^1.0.4apps/mcp/package.json
npm@trusty-squire/skill-schemaworkspace:0.1.6apps/mcp/package.json
npmbetter-sqlite3^12.10.0apps/mcp/package.json
npmboxen^8.0.1apps/mcp/package.json
npmcanonicalize^2.0.0apps/mcp/package.json
npmchalk^5.3.0apps/mcp/package.json
npmjose^5.9.6apps/mcp/package.json
npmjsonc-parser^3.3.1apps/mcp/package.json
npmopen^10.1.0apps/mcp/package.json
npmora^8.1.1apps/mcp/package.json
npmpatchright^1.60.2apps/mcp/package.json
npmplaywright^1.59.0apps/mcp/package.json
npmplaywright-extra^4.3.6apps/mcp/package.json
npmpuppeteer-extra-plugin-stealth^2.11.2apps/mcp/package.json
npmrebrowser-playwright-core^1.52.0apps/mcp/package.json
npmsharp^0.34.5apps/mcp/package.json
npmsmol-toml^1.6.1apps/mcp/package.json
npmtldts^7.0.30apps/mcp/package.json
npmyaml^2.6.1apps/mcp/package.json
npmzod^3.23.8apps/mcp/package.json
npm@trusty-squire/skill-schemaworkspace:*apps/registry/package.json
npm@prisma/client^5.22.0apps/registry/package.json
npmcanonicalize^2.0.0apps/registry/package.json
npmfastify^4.28.0apps/registry/package.json
npmsemver^7.6.3apps/registry/package.json
npmzod^3.23.8apps/registry/package.json
npm@trusty-squire/vaultworkspace:*apps/web/package.json
npm@vouchflow/web0.3.1apps/web/package.json
npmnext16.2.6apps/web/package.json
npmreact19.2.4apps/web/package.json
npmreact-dom19.2.4apps/web/package.json
npmtldts^7.0.30packages/recipe-schema/package.json
npmzod^3.23.8packages/recipe-schema/package.json
npmzod^3.23.8packages/skill-schema/package.json
npm@hpke/core^1.9.0packages/vault/package.json
npm@prisma/client^5.22.0packages/vault/package.json
npmulid^2.3.0packages/vault/package.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 1

Installing npm:@trusty-squire/mcp@1.1.15 pulls in 279 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
sharp0.34.5directhigh20.35.4

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with Trusty-Squire/trusty-squire. Read them side by side →

95Q00/ouroborosAgent OS: the agent gets smarter on its own. We just hold the line: Interview-gated, staged evaluation, budgeted evolution loop. MCP server, 14 runtimes: Claude Code, Codex CLI, Gemini CLI, OpenCode, Copilot, Kiro and more.Exceptional94jgravelle/jcodemunch-mcpCut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP client. 313B+ tokens saved.Exceptional98awslabs/cli-agent-orchestratorMulti-agent orchestration for AI coding CLIs — Claude Code, Kiro, Codex, and more, coordinated in isolated tmux sessionsExceptional97Observal/ObservalObserval is self-hosted registry for your coding agent extensions with a built in insight engine. Setup Observal, define the scope and share your Skills, MCPs and Agents with your peers.Exceptional94openlit/openlitOpen-source observability & evaluation platform for AI agents and coding agents. Trace LLMs, tools, prompts, costs & agent workflows with OpenTelemetry.Exceptional96diegosouzapw/OmniRouteNever stop coding. Free MIT AI gateway: one endpoint, 352 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 550+ contributorsExceptional

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.