Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 14:03 UTC

Arjun0606 / smolanalytics

End-to-end tests without test code. Write one sentence, an agent drives a real browser on every pull request and tells you what broke. A passing run is recorded and replays with no model call. Commercial, hosted at smolanalytics.com.

Go · JavaScriptMIT★ 3 stars⑂ 1 forksince Jun 2026View on GitHub ↗
KindCommand-line toolMCP serverNetwork serviceLibraryhow this is determined

Arjun0606/smolanalytics holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Vitality (81/100) and lowest on Security (30/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Arjun0606Personal account
6 followers43 public repossince Oct 2020

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?

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
7.6/36Commit cadence11/52 weeks with commits
18/18Commit volume568 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year568
human_commit_share1
days_since_last_push0
active_weeks_last_year11

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~2.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv0.92.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.2

Community & Adoption

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

49Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
46.7/80Monthly downloads3,173 downloads/month across go, npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgithub.com/Arjun0606/smolanalytics, smolanalytics
dependents
ecosystemsgo, npm
total_downloads
monthly_downloads3,173
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?

36Weak · 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: Contributorsno data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution0% of issues closed
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs0
open_issues4
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
6.1/25Owner reach6 followers of Arjun0606
23.8/25Track record43 public repos, account ~5 yr old
Inputs used
followers6
owner_typeUser
is_verified
owner_loginArjun0606
public_repos43
account_age_days2,153
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 go, npm
35/35Publish recencylatest publish 0 days ago
20/20Version history177 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/Arjun0606/smolanalytics, smolanalytics
ecosystemsgo, npm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://smolanalytics.com
10/10Repository description
10/10Topics20 topics
0/10Wiki
Inputs used
topicsclaude, cursor, golang, mcp, mcp-server, agentic-testing, ai-testing, browser-automation, ci-cd, e2e-testing, end-to-end-testing, github-actions, no-code-testing, playwright, pull-request, qa, regression-testing, test-automation, testing, vibe-coding
has_wikino
homepagehttps://smolanalytics.com
docs_sitehttps://smolanalytics.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

30At Risk · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestscli/package.json, go.mod
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, docs/agents.md
15/15Machine-readable docs (llms.txt)llms.txt present
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md, docs/agents.md
agent_instruction_max_bytes7,571
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
54.3/55Manageable file sizes6/493 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes119,684
source_files_sampled493
oversized_source_files6
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

3GitHub stars
1contributors
568commits, last 12 months
0days since last push
100releases
1bus factor
4open issues
Go, 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
  • deps.dev does not index npm:smolanalytics@0.21.0; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/Arjun0606/smolanalytics: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-09T14:03:23Z. Please include `CDE8:3989DA:1476C51:13D26D5:6AA16728` when reporting this issue.); skipping Scorecard checks

More detail

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

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 statisticsGo, npm.