Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-23 11:39 UTC

AhmedAyachi / LinkerLine

An extension to the LeaderLine project: adding parent element,scroll positioning, absolute parent positioning

JavaScriptMIT★ 53 stars⑂ 9 forkssince Nov 2023View on GitHub ↗

AhmedAyachi/LinkerLine holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Vitality (67/100) and lowest on AI Readiness (21/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

AhmedAyachiPersonal account
6 followers42 public repossince Feb 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmlinkerline1.6.45,4031439 days agoleaderlinkerlinearrowattentionhighlightspotlightbubblemarkupscrollsvgabsolutepositioningposition

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
28.8/36Push recency — last push 11 days ago
2.1/36Commit cadence — 3/52 weeks with commits
10/18Commit volume — 12 commits in the last year
10/10OpenSSF Scorecard: Maintained — 12 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year12
human_commit_share1
days_since_last_push11
active_weeks_last_year3
How it's scored
27/27Ships releases — 14 releases published
36/36Release recency — latest release 39 days ago
19.8/27Release cadence — a release every ~104.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv1.6.4
releases_from_tagsno
days_since_latest_release39
mean_days_between_releases104.2
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?

54Moderate · 17% of overall
How it's scored
27.8/60Stars — 53 stars
7.5/25Forks — 9 forks
0/15Watchers — 2 watchers
Inputs used
forks9
stars53
watchers2
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_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
49.8/80Monthly downloads — 5,403 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslinkerline
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,403
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.3/22.5Commit distribution — top contributor authored 99% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.988
How it's scored
37/42Issue resolution — 88% of issues closed
20/30PR acceptance — 2/3 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/26 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues2
closed_issues15
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.882
closed_unmerged_prs1
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
6.1/25Owner reach — 6 followers of AhmedAyachi
23.9/25Track record — 42 public repos, account ~6 yr old
Inputs used
followers6
owner_typeUser
is_verified—
owner_loginAhmedAyachi
public_repos42
account_age_days2,444
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

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 — 14 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslinkerline
ecosystemsnpm
any_deprecatedno
min_days_since_publish39

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 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 2 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 2/26 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
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 — 12 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories7
affected_packages4
assessed_packages118
unassessed_packages0
affected_by_severityhigh 2, moderate 1, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 118 resolved dependencies against OSV. 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.

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.

21At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.3/40Legible commit history — 34 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.4
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 85
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
47.1/55Manageable file sizes — 1/7 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes100,113
source_files_sampled7
oversized_source_files1

Key facts

53GitHub stars
2contributors
12commits, last 12 months
11days since last push
14releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
8Releases

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.

0246810922024-052025-072026-09
Major 0Minor 4Patch 4

Each point covers 3 days.

OpenSSF Scorecard 2.8 / 10
2.8aggregate

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-23 11:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 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 2/26 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
3Vulnerabilities7 existing vulnerabilities detected
All dependencies 118

Full resolved dependency set from the GitHub dependency graph: 0 direct and 118 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@discoveryjs/json-ext0.5.7indirect
npm@jridgewell/gen-mapping0.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/set-array1.2.1indirect
npm@jridgewell/source-map0.3.6indirect
npm@jridgewell/sourcemap-codec1.5.0indirect
npm@jridgewell/trace-mapping0.3.25indirect
npm@types/eslint9.6.1indirect
npm@types/eslint-scope3.7.7indirect
npm@types/estree1.0.6indirect
npm@types/json-schema7.0.15indirect
npm@types/node22.10.1indirect
npm@webassemblyjs/ast1.14.1indirect
npm@webassemblyjs/floating-point-hex-parser1.13.2indirect
npm@webassemblyjs/helper-api-error1.13.2indirect
npm@webassemblyjs/helper-buffer1.14.1indirect
npm@webassemblyjs/helper-numbers1.13.2indirect
npm@webassemblyjs/helper-wasm-bytecode1.13.2indirect
npm@webassemblyjs/helper-wasm-section1.14.1indirect
npm@webassemblyjs/ieee7541.13.2indirect
npm@webassemblyjs/leb1281.13.2indirect
npm@webassemblyjs/utf81.13.2indirect
npm@webassemblyjs/wasm-edit1.14.1indirect
npm@webassemblyjs/wasm-gen1.14.1indirect
npm@webassemblyjs/wasm-opt1.14.1indirect
npm@webassemblyjs/wasm-parser1.14.1indirect
npm@webassemblyjs/wast-printer1.14.1indirect
npm@webpack-cli/configtest2.1.1indirect
npm@webpack-cli/info2.0.2indirect
npm@webpack-cli/serve2.0.5indirect
npm@xtuc/ieee7541.2.0indirect
npm@xtuc/long4.2.2indirect
npmacorn8.14.0indirect
npmajv6.12.6indirect
npmajv-keywords3.5.2indirect
npmbrowserslist4.24.2indirect
npmbuffer-from1.1.2indirect
npmcaniuse-lite1.0.30001685indirect
npmchrome-trace-event1.0.4indirect
npmclone-deep4.0.1indirect
npmcolorette2.0.20indirect
npmcommander10.0.1indirect
npmcommander2.20.3indirect
npmcross-spawn7.0.6indirect
npmelectron-to-chromium1.5.67indirect
npmenhanced-resolve5.17.1indirect
npmenvinfo7.14.0indirect
npmes-module-lexer1.5.4indirect
npmescalade3.2.0indirect
npmeslint-scope5.1.1indirect
npmesrecurse4.3.0indirect
npmestraverse4.3.0indirect
npmestraverse5.3.0indirect
npmevents3.3.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfastest-levenshtein1.0.16indirect
npmfind-up4.1.0indirect
npmflat5.0.2indirect
npmfunction-bind1.1.2indirect
npmglob-to-regexp0.4.1indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhasown2.0.2indirect
npmimport-local3.2.0indirect
npminterpret3.1.1indirect
npmis-core-module2.15.1indirect
npmis-plain-object2.0.4indirect
npmisexe2.0.0indirect
npmisobject3.0.1indirect
npmjest-worker27.5.1indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-schema-traverse0.4.1indirect
npmkind-of6.0.3indirect
npmloader-runner4.3.0indirect
npmlocate-path5.0.0indirect
npmmerge-stream2.0.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmneo-async2.6.2indirect
npmnode-releases2.0.18indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-try2.2.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-parse1.0.7indirect
npmpicocolors1.1.1indirect
npmpkg-dir4.2.0indirect
npmpunycode2.3.1indirect
npmrandombytes2.1.0indirect
npmrechoir0.8.0indirect
npmresolve1.22.8indirect
npmresolve-cwd3.0.0indirect
npmresolve-from5.0.0indirect
npmsafe-buffer5.2.1indirect
npmschema-utils3.3.0indirect
npmserialize-javascript6.0.2indirect
npmshallow-clone3.0.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmsupports-color8.1.1indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtapable2.2.1indirect
npmterser5.36.0indirect
npmterser-webpack-plugin5.3.10indirect
npmundici-types6.20.0indirect
npmupdate-browserslist-db1.1.1indirect
npmuri-js4.4.1indirect
npmwatchpack2.4.2indirect
npmwebpack5.96.1indirect
npmwebpack-cli5.1.4indirect
npmwebpack-merge5.10.0indirect
npmwebpack-sources3.2.3indirect
npmwhich2.0.2indirect
npmwildcard2.0.1indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 118 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
browserslist4.24.2indirecthigh24.28.7
serialize-javascript6.0.2indirecthigh27.0.5
ajv6.12.6indirectmoderate18.18.0
webpack5.96.1indirectlow25.104.1

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.