Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 02:33 UTC

LuxAlgo / trade-journal

The open-source trade journal. Broker sync, P&L calendar, deep analytics, and AI reflection. Self-hosted, MIT, free.

TypeScriptMIT★ 398 stars⑂ 151 forkssince Aug 2026View on GitHub ↗
KindWeb interfaceNetwork serviceLibraryhow this is determined

LuxAlgo/trade-journal holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (71/100) and lowest on Security (31/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

LuxAlgoOrganization
605 followers14 public repossince Sep 2020

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

Package ecosystems

Metrics by category

Vitality

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

33At Risk · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
4.2/36Commit cadence — 6/52 weeks with commits
14.5/18Commit volume — 40 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_year40
human_commit_share1
days_since_last_push2
active_weeks_last_year6
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

65Good · 17% of overall
How it's scored
42.2/60Stars — 398 stars
18.1/25Forks — 151 forks
1.7/15Watchers — 3 watchers
Inputs used
forks151
stars398
watchers3
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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
51.2/80Monthly downloads — 6,947 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@luxalgo/journal-core, @luxalgo/journal-importers
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads6,947
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.6/22.5Commit distribution — top contributor authored 57% of commits
5.4/13.5Contributor breadth — 4 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.575
How it's scored
25.2/42Issue resolution — 60% of issues closed
18.3/30PR acceptance — 11/18 decided PRs merged
7.9/13Newcomer PR acceptance — 11/18 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/24 approved changesets -- score normalized to 0
Inputs used
merged_prs11
open_issues4
closed_issues6
prs_merged_7d3
prs_decided_7d4
prs_merged_30d11
prs_decided_30d18
issue_closed_ratio0.6
closed_unmerged_prs7
first_time_authors_30d8
first_time_prs_merged_30d11
first_time_prs_decided_30d18
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
20/25Owner reach — 605 followers of LuxAlgo
20.6/25Track record — 14 public repos, account ~6 yr old
Inputs used
followers605
owner_typeOrganization
is_verifiedno
owner_loginLuxAlgo
public_repos14
account_age_days2,216
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 35 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@luxalgo/journal-core, @luxalgo/journal-importers
ecosystemsnpm
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsbroker, pnl, pnl-tracker, trade-journal, trading-journaling
has_wikino
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?

31At Risk · 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
2.5/2.5CI-Tests — 11 out of 11 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 2/24 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
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
0/5Packaging — no data
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
36/40Legible commit history — 27 of 40 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.675
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — apps/web/tsconfig.json, packages/core/tsconfig.json, packages/importers/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
5/10Demonstrated agent practice — 1 of the last 40 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_configno
typecheck_configsapps/web/tsconfig.json, packages/core/tsconfig.json, packages/importers/tsconfig.json
agent_commit_share0.025
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/308 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes53,101
source_files_sampled308
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

398GitHub stars
4contributors
40commits, last 12 months
2days since last push
0releases
1bus factor
4open 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 ★ / 151 ⇿
0Stars
151Forks

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.

04080120160151372026-092026-092026-10
OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-03 02:33 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 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 2/24 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
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
npm@ai-sdk/anthropic^4.0.41apps/web/package.json
npm@ai-sdk/openai^4.0.64apps/web/package.json
npm@dnd-kit/core6.3.1apps/web/package.json
npm@dnd-kit/sortable10.0.0apps/web/package.json
npm@luxalgo/broker-sdk0.5.1apps/web/package.json
npm@luxalgo/journal-coreworkspace:*apps/web/package.json
npm@luxalgo/journal-importersworkspace:*apps/web/package.json
npm@luxalgo/vela^0.6.8apps/web/package.json
npm@pdf-lib/fontkit^1.1.1apps/web/package.json
npm@radix-ui/react-checkbox^1.3.11apps/web/package.json
npm@radix-ui/react-dialog^1.1.23apps/web/package.json
npm@radix-ui/react-dropdown-menu^2.1.24apps/web/package.json
npm@radix-ui/react-label^2.1.15apps/web/package.json
npm@radix-ui/react-popover^1.1.23apps/web/package.json
npm@radix-ui/react-select^2.3.7apps/web/package.json
npm@radix-ui/react-slot^1.3.3apps/web/package.json
npm@radix-ui/react-tabs^1.1.21apps/web/package.json
npm@radix-ui/react-tooltip^1.2.16apps/web/package.json
npm@tanstack/react-table^9.1.2apps/web/package.json
npmai^7.0.77apps/web/package.json
npmbetter-sqlite3^12.2.0apps/web/package.json
npmclass-variance-authority^0.7.1apps/web/package.json
npmclsx^2.1.1apps/web/package.json
npmdrizzle-orm^0.45.2apps/web/package.json
npmecharts^6.1.0apps/web/package.json
npmlucide-react^1.34.0apps/web/package.json
npmnext^15.5.0apps/web/package.json
npmpdf-lib^1.17.1apps/web/package.json
npmreact^19.1.0apps/web/package.json
npmreact-day-picker^9.14.0apps/web/package.json
npmreact-dom^19.1.0apps/web/package.json
npmreact-markdown^10.1.0apps/web/package.json
npmrecharts^3.10.1apps/web/package.json
npmremark-gfm^4.0.1apps/web/package.json
npmtailwind-merge^3.6.0apps/web/package.json
npm@luxalgo/journal-coreworkspace:*packages/importers/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 — npm.