Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 01:55 UTC

adzerk / adzerk-api-specification

Kevel OpenAPI specification

JavaScriptNo license detected★ 7 stars⑂ 6 forkssince Nov 2019View on GitHub ↗

adzerk/adzerk-api-specification holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (65/100) and lowest on Community & Adoption (26/100). It was last updated 90 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

KevelOrganization
38 followers59 public repossince Dec 2009

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

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
18/36Push recency — last push 90 days ago
7.6/36Commit cadence — 11/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year42
human_commit_share0.99
days_since_last_push90
active_weeks_last_year11
How it's scored
27/27Ships releases — 29 releases published
27/36Release recency — latest release 95 days ago
19.8/27Release cadence — a release every ~46.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count29
latest_release_tagv1.0.30
releases_from_tagsno
days_since_latest_release95
mean_days_between_releases46.1
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?

26At Risk · 17% of overall
How it's scored
12.6/60Stars — 7 stars
5.8/25Forks — 6 forks
8/15Watchers — 28 watchers
Inputs used
forks6
stars7
watchers28
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
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?

65Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.7/22.5Commit distribution — top contributor authored 44% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled15
top_contributor_share0.435
How it's scored
21/42Issue resolution — 50% of issues closed
24.9/30PR acceptance — 88/106 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs88
open_issues3
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs18
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
30/30Ownership backing — organization-owned
0/20Verified domain
11.4/25Owner reach — 38 followers of adzerk
24.9/25Track record — 59 public repos, account ~16 yr old
Inputs used
followers38
owner_typeOrganization
is_verifiedno
owner_loginadzerk
public_repos59
account_age_days6,189

Engineering Quality

Are baseline engineering and documentation practices in place?

43Weak · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 2 out of 7 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://dev.kevel.com
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicskevel-public
has_wikino
homepagehttps://dev.kevel.com
docs_sitehttps://dev.kevel.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.5/2.5CI-Tests — 2 out of 7 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 9 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packaging — packaging workflow detected
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 36 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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
advisories36
affected_packages8
assessed_packages143
unassessed_packages0
affected_by_severitycritical 1, high 4, moderate 3
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 143 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://dev.kevel.com/llms.txt)
18.9/40Legible commit history — 35 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://dev.kevel.com/llms.txt
legible_history_share0.354
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
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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.03
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes1,529
source_files_sampled2
oversized_source_files0

Key facts

7GitHub stars
15contributors
42commits, last 12 months
90days since last push
29releases
2bus factor
3open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@adzerk/api-specification' from its registry

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
29Releases

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.

123456612020-102023-102026-09
Major 0Minor 0Patch 29

Each point covers 6 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-11-17 01:55 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
2CI-Tests2 out of 7 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities36 existing vulnerabilities detected
All dependencies 143

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

RegistryPackageVersionRelation
npm@borewit/text-codec0.2.2indirect
npm@inquirer/core6.0.0indirect
npm@inquirer/select1.3.3indirect
npm@inquirer/type1.5.5indirect
npm@lukeed/csprng1.1.0indirect
npm@nestjs/axios4.0.1indirect
npm@nestjs/common11.1.27indirect
npm@nestjs/core11.1.27indirect
npm@nuxtjs/opencollective0.3.2indirect
npm@openapitools/openapi-generator-cli2.39.1indirect
npm@tokenizer/inflate0.4.1indirect
npm@tokenizer/token0.3.0indirect
npm@types/mute-stream0.0.4indirect
npm@types/node20.19.42indirect
npm@types/wrap-ansi3.0.0indirect
npmagent-base6.0.2indirect
npmagent-base9.0.0indirect
npmansi-escapes4.3.2indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmast-types0.13.4indirect
npmasynckit0.4.0indirect
npmaxios1.18.1indirect
npmbalanced-match4.0.4indirect
npmbasic-ftp5.3.1indirect
npmbrace-expansion5.0.6indirect
npmcall-bind-apply-helpers1.0.2indirect
npmchalk4.1.2indirect
npmchalk5.6.2indirect
npmcli-spinners2.9.2indirect
npmcli-width4.1.0indirect
npmcliui9.0.1indirect
npmclone1.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcombined-stream1.0.8indirect
npmcommander8.3.0indirect
npmcompare-versions6.1.1indirect
npmconcurrently10.0.3indirect
npmconsola2.15.3indirect
npmconsole.table0.10.0indirect
npmdata-uri-to-buffer8.0.0indirect
npmdebug4.4.3indirect
npmdefaults1.0.4indirect
npmdegenerator7.0.1indirect
npmdelayed-stream1.0.0indirect
npmdunder-proto1.0.1indirect
npmeasy-table1.1.0indirect
npmemoji-regex10.6.0indirect
npmemoji-regex8.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmes-set-tostringtag2.1.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp1.0.5indirect
npmescodegen2.1.0indirect
npmesprima4.0.1indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-safe-stringify2.1.1indirect
npmfigures3.2.0indirect
npmfile-type21.3.4indirect
npmfollow-redirects1.16.0indirect
npmform-data4.0.6indirect
npmfs-extra11.3.6indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmget-uri8.0.1indirect
npmglob13.0.6indirect
npmgopd1.2.0indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.4indirect
npmhttp-proxy-agent9.1.0indirect
npmhttps-proxy-agent5.0.1indirect
npmhttps-proxy-agent9.1.0indirect
npmieee7541.2.1indirect
npmip-address10.2.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmiterare1.2.1indirect
npmjsonfile6.2.1indirect
npmload-esm1.0.3indirect
npmlru-cache11.5.1indirect
npmlru-cache7.18.3indirect
npmmath-intrinsics1.1.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmminimatch10.2.5indirect
npmminipass7.1.3indirect
npmms2.1.3indirect
npmmute-stream1.0.0indirect
npmnetmask2.1.1indirect
npmnode-fetch2.7.0indirect
npmpac-proxy-agent9.1.0indirect
npmpac-resolver9.0.1indirect
npmpath-scurry2.0.2indirect
npmpath-to-regexp8.4.2indirect
npmproxy-agent8.0.2indirect
npmproxy-agent-negotiate1.1.0indirect
npmproxy-from-env2.1.0indirect
npmquickjs-wasi2.2.0indirect
npmreflect-metadata0.2.2indirect
npmrun-async3.0.0indirect
npmrxjs7.8.2indirect
npmshell-quote1.8.4indirect
npmsignal-exit4.1.0indirect
npmsmart-buffer4.2.0indirect
npmsocks2.8.9indirect
npmsocks-proxy-agent10.1.0indirect
npmsource-map0.6.1indirect
npmstring-width4.2.3indirect
npmstring-width7.2.0indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrtok310.3.5indirect
npmsupports-color10.2.2indirect
npmsupports-color7.2.0indirect
npmtoken-types6.1.2indirect
npmtr460.0.3indirect
npmtree-kill1.2.2indirect
npmtslib2.8.1indirect
npmtype-fest0.21.3indirect
npmtypescript5.2.2indirect
npmuid2.0.2indirect
npmuint8array-extras1.5.0indirect
npmundici-types6.21.0indirect
npmuniversalify2.0.1indirect
npmwcwidth1.0.1indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwrap-ansi6.2.0indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyargs18.0.0indirect
npmyargs-parser22.0.0indirect
Dependency advisories 8

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

PackageVersionRelationSeverityAdvisoriesFixed in
shell-quote1.8.4indirectcritical21.11.0
axios1.18.1indirecthigh121.20.0
basic-ftp5.3.1indirecthigh36.2.4
brace-expansion5.0.6indirecthigh65.0.12
follow-redirects1.16.0indirecthigh31.16.2
glob13.0.6indirectmoderate114.0.2
ip-address10.2.0indirectmoderate810.7.4
minimatch10.2.5indirectmoderate111.0.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.