n4ze3m/page-assist holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on Security (32/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.
65
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.
65
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)
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 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.
Direct dependencies free of known advisories — 1 affected: pdfjs-dist 4.0.379 (high 8.8)
0/25
Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
32.8/40
No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 842 days ago
Inputs used
source
osv
advisories
1
affected_packages
1
assessed_packages
16
unassessed_packages
70
affected_by_severity
high 1
direct_affected_packages
1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 16 resolved dependencies against OSV. 70 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.
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.
API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20
MCP server
0/40
Runnable examples
Inputs used
example_dirs
—
has_mcp_signal
yes
api_schema_files
—
interfaces_expected_of
—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.
Key facts
8,182GitHub stars
41contributors
359commits, last 12 months
4days since last push
100releases
1bus factor
344open issues
npmpackage ecosystems
Data collection warnings
Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Could not fetch npm package 'pageassist' from its registry
More detail
Star and fork history 0 ★ / 780 ⇿
0Stars
780Forks
100Releases
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.
Major 0Minor 3Patch 97
Each point covers 4 days.
OpenSSF Scorecard 2.6 / 10
2.6aggregate
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-08-28 02:22 UTC
Full resolved dependency set from the GitHub dependency graph: 60 direct and 26 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
Registry
Package
Version
Relation
npm
@ant-design/cssinjs
^1.18.4
direct
npm
@cfworker/json-schema
^4.1.1
direct
npm
@headlessui/react
^1.7.18
direct
npm
@heroicons/react
^2.1.1
direct
npm
@langchain/community
^1.1.22
direct
npm
@langchain/core
^1.1.31
direct
npm
@langchain/openai
^1.2.12
direct
npm
@mantine/form
^7.5.0
direct
npm
@mantine/hooks
^7.5.3
direct
npm
@modelcontextprotocol/sdk
^1.27.1
direct
npm
@modelcontextprotocol/sdk
^1.29.0
direct
npm
@plasmohq/storage
^1.9.0
direct
npm
@tailwindcss/forms
^0.5.7
direct
npm
@tailwindcss/typography
^0.5.10
direct
npm
@tanstack/react-query
^5.17.19
direct
npm
@tanstack/react-virtual
^3.13.6
direct
npm
@vitejs/plugin-react
^4.2.1
direct
npm
antd
^5.13.3
direct
npm
axios
^1.6.7
direct
npm
caniuse-lite
^1.0.30001716
direct
npm
cheerio
^1.0.0-rc.12
direct
npm
d3-dsv
2
direct
npm
dayjs
^1.11.10
direct
npm
defuddle
^0.18.1
direct
npm
dexie
^4.0.11
direct
npm
dexie-react-hooks
^1.1.7
direct
npm
html-to-text
^9.0.5
direct
npm
html2canvas
^1.4.1
direct
npm
i18next
^23.10.1
direct
npm
i18next-browser-languagedetector
^7.2.0
direct
npm
langchain
^1.2.30
direct
npm
lucide-react
^0.350.0
direct
npm
mammoth
^1.7.2
direct
npm
marked
^15.0.12
direct
npm
mermaid
^11.4.1
direct
npm
ml-distance
^4.0.1
direct
npm
ollama
^0.5.17
direct
npm
openai
^4.95.1
direct
npm
pa-tesseract.js
^5.1.1
direct
npm
pdfjs-dist
4.0.379
direct
npm
property-information
^6.4.1
direct
npm
pubsub-js
^1.9.4
direct
npm
react
18.2.0
direct
npm
react
^19.2.4
direct
npm
react-dom
18.2.0
direct
npm
react-dom
^19.2.4
direct
npm
react-i18next
^14.1.0
direct
npm
react-icons
^5.2.1
direct
npm
react-markdown
8.0.0
direct
npm
react-router-dom
6.10.0
direct
npm
react-syntax-highlighter
^15.5.0
direct
npm
react-toastify
^10.0.4
direct
npm
rehype-katex
6.0.3
direct
npm
rehype-mathjax
4.0.3
direct
npm
remark-gfm
3.0.1
direct
npm
remark-math
5.1.1
direct
npm
turndown
^7.1.3
direct
npm
unist-util-visit
^5.0.0
direct
npm
yt-transcript
^0.0.2
direct
npm
zustand
^4.5.0
direct
npm
@plasmohq/prettier-plugin-sort-imports
4.0.1
indirect
npm
@types/chrome
^0.0.280
indirect
npm
@types/chrome
^0.1.43
indirect
npm
@types/d3-dsv
^3.0.7
indirect
npm
@types/html-to-text
^9.0.4
indirect
npm
@types/node
20.11.9
indirect
npm
@types/pubsub-js
^1.8.6
indirect
npm
@types/react
18.2.48
indirect
npm
@types/react
^19.2.14
indirect
npm
@types/react-dom
18.2.18
indirect
npm
@types/react-dom
^19.2.3
indirect
npm
@types/react-speech-recognition
^3.9.5
indirect
npm
@types/react-syntax-highlighter
^15.5.11
indirect
npm
@types/turndown
^5.0.4
indirect
npm
@wxt-dev/module-react
^1.1.5
indirect
npm
autoprefixer
^10.4.17
indirect
npm
cross-env
^7.0.3
indirect
npm
postcss
^8.4.33
indirect
npm
prettier
3.2.4
indirect
npm
tailwindcss
^3.4.1
indirect
npm
typescript
5.3.3
indirect
npm
typescript
^5.9.3
indirect
npm
vite-plugin-top-level-await
^1.4.1
indirect
npm
vitepress
^1.6.3
indirect
npm
wxt
^0.19.6
indirect
npm
wxt
^0.20.26
indirect
Dependency advisories 1
This repository publishes no package the index resolves, so its own dependency graph was assessed — 16 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct. 70 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.
Package
Version
Relation
Severity
Advisories
Fixed in
pdfjs-dist
4.0.379
direct
high
1
4.2.67
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.
Related records
Inspected repositories sharing catalogue tags or ecosystems with n4ze3m/page-assist. Read them side by side →
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.
