Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-17 21:13 UTC

probelabs / visor

Visor — AI workflow engine for code review, assistants, and automation. Orchestrates checks, MCP tools, and AI providers with YAML-driven pipelines. Runs as GitHub Action, CLI, Slack bot, or HTTP API.

TypeScriptMIT★ 24 stars⑂ 2 forkssince Sep 2025View on GitHub ↗
KindCommand-line toolLibraryMCP serverChat botTerminal interfacehow this is determined

probelabs/visor holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (87/100) and lowest on Security (39/100). It was last updated 14 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ProbeOrganization
23 followers35 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@probelabs/visor0.1.1936,00322239 days agocode-reviewaigithub-actionclipr-reviewvisor

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 14 days ago
21.5/36Commit cadence — 31/52 weeks with commits
18/18Commit volume — 829 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year829
human_commit_share0.99
days_since_last_push14
active_weeks_last_year31

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 14 days ago
27/27Release cadence — a release every ~21.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.1.194
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases21.7
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?

49Weak · 17% of overall
How it's scored
22.1/60Stars — 24 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars24
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)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
50.4/80Monthly downloads — 6,003 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@probelabs/visor
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads6,003
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.7/22.5Commit distribution — top contributor authored 57% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.57
How it's scored
39.7/42Issue resolution — 95% of issues closed
23.5/30PR acceptance — 415/529 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs415
open_issues2
closed_issues35
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.946
closed_unmerged_prs114
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
30/30Ownership backing — organization-owned
0/20Verified domain
9.9/25Owner reach — 23 followers of probelabs
13.7/25Track record — 35 public repos, account ~1 yr old
Inputs used
followers23
owner_typeOrganization
is_verifiedno
owner_loginprobelabs
public_repos35
account_age_days428

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 39 days ago
20/20Version history — 222 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@probelabs/visor
ecosystemsnpm
any_deprecatedno
min_days_since_publish39

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
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 site — https://probelabs.com/visor
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsai, automation, cli, code-review, github-actions, typescript, ai-agents, mcp, slack-bot, workflow-engine
has_wikiyes
homepagehttps://probelabs.com/visor
docs_sitehttps://probelabs.com/visor
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

39Weak · 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
0/2.5CI-Tests — 0 out of 4 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
0/7.5Code-Review — Found 0/3 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
5/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 — 293 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
8.2/35Direct dependencies free of known advisories — 4 affected: @opentelemetry/sdk-node 0.203.0 (high 7.5), nodemailer 8.0.11 (high 7.5), simple-git 3.36.0 (high 8.1), +1 more
2.3/25Indirect dependencies free of known advisories — 13 affected: @fastify/busboy 2.1.1 (high 7.5), @opentelemetry/exporter-prometheus 0.203.0 (high 7.5), @opentelemetry/propagator-jaeger 2.0.1 (high 7.5), +10 more
13.3/40No advisories left outstanding — 11 advisory-carrying package(s) unaddressed past 90 days; oldest published 276 days ago
Inputs used
sourceosv
advisories58
affected_packages17
assessed_packages614
unassessed_packages0
affected_by_severityhigh 14, moderate 3
direct_affected_packages4
Matched the npm:@probelabs/visor@0.1.193 runtime dependency closure — what installing the published package pulls in — 614 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.

74Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 85 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.859
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes7,714
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
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_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
52.8/55Manageable file sizes — 30/763 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes254,330
source_files_sampled763
oversized_source_files30
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofchat-bot

Key facts

24GitHub stars
5contributors
829commits, last 12 months
14days since last push
100releases
1bus factor
2open 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

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
69Releases

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.

111222212025-102026-012026-03
Major 0Minor 0Patch 69
OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-10-17 21:13 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities293 existing vulnerabilities detected
Direct dependencies 57
RegistryPackageVersion constraintManifest
npm@actions/core^1.11.1package.json
npm@apidevtools/swagger-parser^12.1.0package.json
npm@grammyjs/runner^2.0.3package.json
npm@modelcontextprotocol/sdk^1.25.3package.json
npm@nyariv/sandboxjsgithub:probelabs/SandboxJS#d0d8c8ab3113d3b73e08b79b88a4b834ba3fae11package.json
npm@octokit/action^8.0.2package.json
npm@octokit/auth-app^8.1.0package.json
npm@octokit/core^7.0.3package.json
npm@octokit/rest^22.0.0package.json
npm@opentelemetry/api^1.9.0package.json
npm@opentelemetry/api-logs^0.203.0package.json
npm@opentelemetry/core^1.30.1package.json
npm@opentelemetry/exporter-logs-otlp-http^0.203.0package.json
npm@opentelemetry/exporter-metrics-otlp-http^0.203.0package.json
npm@opentelemetry/exporter-trace-otlp-grpc^0.203.0package.json
npm@opentelemetry/exporter-trace-otlp-http^0.203.0package.json
npm@opentelemetry/instrumentation^0.203.0package.json
npm@opentelemetry/resources^1.30.1package.json
npm@opentelemetry/sdk-logs^0.203.0package.json
npm@opentelemetry/sdk-metrics^1.30.1package.json
npm@opentelemetry/sdk-node^0.203.0package.json
npm@opentelemetry/sdk-trace-base^1.30.1package.json
npm@opentelemetry/semantic-conventions^1.30.1package.json
npm@probelabs/probe0.6.0-rc341package.json
npm@types/commander^2.12.0package.json
npm@types/uuid^10.0.0package.json
npm@utcp/file^1.1.0package.json
npm@utcp/http^1.1.0package.json
npm@utcp/sdk^1.1.0package.json
npm@utcp/text^1.1.0package.json
npmacorn^8.16.0package.json
npmacorn-walk^8.3.5package.json
npmajv^8.17.1package.json
npmajv-formats^3.0.1package.json
npmbetter-sqlite3^11.0.0package.json
npmblessed^0.1.81package.json
npmbotbuilder^4.23.3package.json
npmbotframework-connector^4.23.3package.json
npmcli-table3^0.6.5package.json
npmcommander^14.0.0package.json
npmdeepmerge^4.3.1package.json
npmdotenv^17.2.3package.json
npmgrammy^1.41.1package.json
npmignore^7.0.5package.json
npmimapflow^1.2.12package.json
npmjs-yaml^4.1.0package.json
npmjsonpath-plus^10.4.0package.json
npmliquidjs^10.21.1package.json
npmmailparser^3.9.3package.json
npmminimatch^10.2.2package.json
npmnode-cron^3.0.3package.json
npmnodemailer^8.0.1package.json
npmopen^9.1.0package.json
npmresend^6.9.3package.json
npmsimple-git^3.28.0package.json
npmuuid^11.1.0package.json
npmws^8.18.3package.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 17

Installing npm:@probelabs/visor@0.1.193 pulls in 614 packages, direct and transitive: 17 carry known advisories, of which 4 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@opentelemetry/sdk-node0.203.0directhigh10.217.0
nodemailer8.0.11directhigh810.0.6
simple-git3.36.0directhigh34.0.1
@fastify/busboy2.1.1indirecthigh23.2.2
@opentelemetry/exporter-prometheus0.203.0indirecthigh10.217.0
@opentelemetry/propagator-jaeger2.0.1indirecthigh12.9.0
@simple-git/argv-parser1.1.1indirecthigh12.0.1
adm-zip0.5.18indirecthigh80.6.1
braces3.0.3indirecthigh1—
lodash-es4.17.23indirecthigh24.18.0
tar6.2.1indirecthigh127.5.21
undici5.29.0indirecthigh138.10.2
uuid10.0.0indirecthigh113.0.1
uuid8.3.2indirecthigh113.0.1
@opentelemetry/core1.30.1directmoderate12.8.0
@opentelemetry/core2.0.1indirectmoderate12.8.0
sprintf-js1.1.3indirectmoderate1—

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.