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

xang1234 / stock-screener

Stock scanner with multiple fundamental and technical criteria. Features 80+ filters, AI chatbot (Groq/DeepSeek/Gemini), theme discovery, and StockBee-style breadth indicators.

Python · JavaScriptApache-2.0★ 310 stars⑂ 104 forkssince Jan 2026View on GitHub ↗
KindWeb interfacehow this is determined

xang1234/stock-screener holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Security (25/100). It was last updated today. 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

D TPersonal account
65 followers38 public repossince Oct 2016

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

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume2,515 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year2,515
human_commit_share1
days_since_last_push0
active_weeks_last_year30

Release discipline

100Exceptional
How it's scored
27/27Ships releases16 releases published
36/36Release recencylatest release 7 days ago
27/27Release cadencea release every ~13.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv1.6.0
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases13.1

Community & Adoption

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

65Good · 17% of overall
How it's scored
40.4/60Stars310 stars
16.8/25Forks104 forks
2.7/15Watchers4 watchers
Inputs used
forks104
stars310
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.1/22.5Commit distributiontop contributor authored 95% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.952
How it's scored
36.8/42Issue resolution88% of issues closed
28.9/30PR acceptance309/321 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs309
open_issues5
closed_issues35
prs_merged_7d3
prs_decided_7d4
prs_merged_30d18
prs_decided_30d20
issue_closed_ratio0.875
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
13.1/25Owner reach65 followers of xang1234
23.6/25Track record38 public repos, account ~9 yr old
Inputs used
followers65
owner_typeUser
is_verified
owner_loginxang1234
public_repos38
account_age_days3,631
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
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_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://xang1234.github.io/stock-screener/
10/10Repository description
10/10Topics11 topics
0/10Wiki
Inputs used
topicscanslim, market-breadth, minervini, stock-analysis, stock-screener, trading, finance, investment, trading-automation, nasdaq-stocks, nyse-stocks
has_wikino
homepagehttps://xang1234.github.io/stock-screener/
docs_sitehttps://xang1234.github.io/stock-screener/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

25At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfilespackage-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestsbackend/requirements-runtime.txt, backend/requirements-server.txt, backend/requirements-test.txt, backend/requirements-theme-ml.txt, backend/requirements.txt, frontend/package.json
has_codeql_workflowno
has_security_policyno
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.

66Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history93 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.93
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes12,734
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configeslint.config.js
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
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
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
54.4/55Manageable file sizes21/1,908 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes154,256
source_files_sampled1,908
oversized_source_files21
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

310GitHub stars
3contributors
2,515commits, last 12 months
0days since last push
16releases
1bus factor
5open issues
npm, PyPIpackage 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
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 104 ⇿
0Stars
104Forks
16Releases

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.

020406080100120103132026-022026-052026-09
Major 1Minor 6Patch 2
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@emotion/react^11.11.3frontend/package.json
npm@emotion/styled^11.11.0frontend/package.json
npm@hello-pangea/dnd^18.0.1frontend/package.json
npm@mui/icons-material^5.18.0frontend/package.json
npm@mui/material^5.15.3frontend/package.json
npm@tanstack/query-sync-storage-persister^5.101.0frontend/package.json
npm@tanstack/react-query^5.101.0frontend/package.json
npm@tanstack/react-query-persist-client^5.101.0frontend/package.json
npm@tanstack/react-table^8.11.6frontend/package.json
npm@tanstack/react-virtual^3.13.18frontend/package.json
npmajv^8.17.1frontend/package.json
npmajv-formats^3.0.1frontend/package.json
npmaxios1.13.2frontend/package.json
npmdate-fns^4.1.0frontend/package.json
npmlightweight-charts^5.1.0frontend/package.json
npmreact^18.3.1frontend/package.json
npmreact-dom^18.3.1frontend/package.json
npmreact-markdown^9.1.0frontend/package.json
npmreact-router-dom^6.21.0frontend/package.json
npmrecharts^2.15.4frontend/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

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.