Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 14:26 UTC

akamai / cli

Manage and configure Akamai from the Command Line.

GoApache-2.0★ 238 stars⑂ 86 forkssince May 2017View on GitHub ↗

KindCommand-line toolLibraryhow this is determined

#cli #akamai #devexp-cli #devexp #akamai-cli #akamai-devexp

akamai/cli holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (79/100) and lowest on Community & Adoption (57/100). It was last updated 34 days ago. 2 contributors account for most of its recent work.

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.

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

Ownership

AkamaiOrganization

618 followers206 public repossince Sep 2013

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
Go	github.com/akamai/cli/v2	v2.0.5	-	6	58 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall

Development activity

48Weak

How it's scored

18/36	Push recency — last push 34 days ago
11.1/36	Commit cadence — 16/52 weeks with commits
13.8/18	Commit volume — 33 commits in the last year
5/10	OpenSSF Scorecard: Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5

Inputs used

commits_last_year	33
human_commit_share	0.95
days_since_last_push	34
active_weeks_last_year	16

Release discipline

84Excellent

How it's scored

27/27	Ships releases — 41 releases published
36/36	Release recency — latest release 58 days ago
12.6/27	Release cadence — a release every ~124.6 days
8/10	OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.

Inputs used

releases_count	41
latest_release_tag	v2.0.5
releases_from_tags	no
days_since_latest_release	58
mean_days_between_releases	124.6

Community & Adoption

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

57Moderate · 17% of overall

Popularity & adoption

63Moderate

How it's scored

38.5/60	Stars — 238 stars
16.1/25	Forks — 86 forks
8.8/15	Watchers — 40 watchers

Inputs used

forks	86
stars	238
watchers	40
growth_state	organic
growth_factor_pct	100

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	4
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, goreportcard.com, shields.io
has_pull_request_template	no

Sustainability & Governance

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

79Good · 23% of overall

Maintainer resilience (bus factor)

64Moderate

How it's scored

25.2/54	Bus factor — 2 contributor(s) cover half of all commits
14.8/22.5	Commit distribution — top contributor authored 34% of commits
13.5/13.5	Contributor breadth — 36 contributors
10/10	OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	36
top_contributor_share	0.341

Issue & PR responsiveness

85Excellent

How it's scored

41.7/42	Issue resolution — 99% of issues closed
17.1/30	PR acceptance — 53/93 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	53
open_issues	1
closed_issues	122
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.992
closed_unmerged_prs	40
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

75Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
20.1/25	Owner reach — 618 followers of akamai
25/25	Track record — 206 public repos, account ~12 yr old

Inputs used

followers	618
owner_type	Organization
is_verified	no
owner_login	akamai
public_repos	206
account_age_days	4,740

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on go
35/35	Publish recency — latest publish 58 days ago
20/20	Version history — 6 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	github.com/akamai/cli/v2
ecosystems	go
any_deprecated	no
min_days_since_publish	58

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall

Engineering practices

84Excellent

How it's scored

24/24	CI workflows — 1 workflow(s)
24/24	Tests present
16/16	Linter config — .golangci.yaml
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://techdocs.akamai.com/developer/docs/about-clis
10/10	Repository description
10/10	Topics — 6 topics
0/10	Wiki

Inputs used

topics	cli, akamai, devexp-cli, devexp, akamai-cli, akamai-devexp
has_wiki	no
homepage	https://techdocs.akamai.com/developer/docs/about-clis
docs_site	https://techdocs.akamai.com/developer/docs/about-clis
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

59Moderate · 16% of overall

Security posture

56Moderate

How it's scored

6.8/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
2.5/2.5	Contributors — project has 8 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
3.8/7.5	Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
6/7.5	Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
3/7.5	Vulnerabilities — 6 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	5.6

Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

73Good

How it's scored

15.1/35	Direct dependencies free of known advisories — 1 affected: github.com/go-git/go-git/v5 v5.19.1 (high 7.1)
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40	No advisories left outstanding — no advisory has been public longer than 90 days

Inputs used

source	osv
advisories	4
affected_packages	1
assessed_packages	43
unassessed_packages	0
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 43 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.

66Good · 4% of overall

Agent context & guidance

29At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15	Machine-readable docs (llms.txt) — llms.txt served by the project website (https://techdocs.akamai.com/llms.txt)
14/40	Legible commit history — 25 of 95 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	yes
llms_txt_url	https://techdocs.akamai.com/llms.txt
legible_history_share	0.263
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

80Excellent

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
11/11	Lint / format config — .golangci.yaml
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	go.sum
has_dockerfile	no
typed_language	yes
bootstrap_files	Makefile
has_devcontainer	no
has_linter_config	yes
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0.05

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Go (statically typed)
55/55	Manageable file sizes — 0/80 source files over 60KB

Inputs used

primary_language	Go
largest_source_bytes	38,757
source_files_sampled	80
oversized_source_files	0

Key facts

238GitHub stars

36contributors

33commits, last 12 months

34days since last push

41releases

2bus factor

1open issues

Gopackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Star history carried forward from 2026-06-25: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 238 stars today.

More detail

Star and fork history 236 ★ / 86 ⇿

236Stars

86Forks

40Releases

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.

Star history is shown as collected on 2026-06-25. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

Major 2Minor 11Patch 27

Each point covers 9 days.

OpenSSF Scorecard 5.6 / 10

5.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-09-12 14:25 UTC

9	Binary-Artifacts	binaries present in source code
n/a	Branch-Protection	internal 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
10	CI-Tests	6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
10	Contributors	project has 8 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
5	Maintained	6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
8	Signed-Releases	5 out of the last 5 releases have a total of 5 signed artifacts.
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
4	Vulnerabilities	6 existing vulnerabilities detected

Direct dependencies 15

Registry	Package	Version constraint	Manifest
Go	github.com/AlecAivazis/survey/v2	`v2.3.7`	go.mod
Go	github.com/Masterminds/semver	`v1.5.0`	go.mod
Go	github.com/briandowns/spinner	`v1.23.2`	go.mod
Go	github.com/fatih/color	`v1.18.0`	go.mod
Go	github.com/go-git/go-git/v5	`v5.19.1`	go.mod
Go	github.com/go-ini/ini	`v1.67.0`	go.mod
Go	github.com/inconshreveable/go-update	`v0.0.0-20160112193335-8152e7eb6ccf`	go.mod
Go	github.com/kardianos/osext	`v0.0.0-20190222173326-2bc1f35cddc0`	go.mod
Go	github.com/mattn/go-colorable	`v0.1.14`	go.mod
Go	github.com/mattn/go-isatty	`v0.0.20`	go.mod
Go	github.com/mitchellh/go-homedir	`v1.1.0`	go.mod
Go	github.com/stretchr/testify	`v1.11.1`	go.mod
Go	github.com/urfave/cli/v2	`v2.19.3`	go.mod
Go	golang.org/x/sys	`v0.47.0`	go.mod
Go	golang.org/x/text	`v0.40.0`	go.mod

All dependencies 43

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

Registry	Package	Version	Relation
Go	github.com/alecaivazis/survey/v2	`v2.3.7`	direct
Go	github.com/briandowns/spinner	`v1.23.2`	direct
Go	github.com/fatih/color	`v1.18.0`	direct
Go	github.com/go-git/go-git/v5	`v5.19.1`	direct
Go	github.com/go-ini/ini	`v1.67.0`	direct
Go	github.com/inconshreveable/go-update	`v0.0.0-20160112193335-8152e7eb6ccf`	direct
Go	github.com/kardianos/osext	`v0.0.0-20190222173326-2bc1f35cddc0`	direct
Go	github.com/masterminds/semver	`v1.5.0`	direct
Go	github.com/mattn/go-colorable	`v0.1.14`	direct
Go	github.com/mattn/go-isatty	`v0.0.20`	direct
Go	github.com/mitchellh/go-homedir	`v1.1.0`	direct
Go	github.com/stretchr/testify	`v1.11.1`	direct
Go	github.com/urfave/cli/v2	`v2.19.3`	direct
Go	golang.org/x/sys	`v0.47.0`	direct
Go	golang.org/x/text	`v0.40.0`	direct
Go	dario.cat/mergo	`v1.0.2`	indirect
Go	github.com/cloudflare/circl	`v1.6.3`	indirect
Go	github.com/cpuguy83/go-md2man/v2	`v2.0.7`	indirect
Go	github.com/cyphar/filepath-securejoin	`v0.6.1`	indirect
Go	github.com/davecgh/go-spew	`v1.1.2-0.20180830191138-d8f796af33cc`	indirect
Go	github.com/emirpasic/gods	`v1.18.1`	indirect
Go	github.com/go-git/gcfg	`v1.5.1-0.20230307220236-3a3c6141e376`	indirect
Go	github.com/go-git/go-billy/v5	`v5.9.0`	indirect
Go	github.com/golang/groupcache	`v0.0.0-20241129210726-2c02b8208cf8`	indirect
Go	github.com/jbenet/go-context	`v0.0.0-20150711004518-d14ea06fba99`	indirect
Go	github.com/kballard/go-shellquote	`v0.0.0-20180428030007-95032a82bc51`	indirect
Go	github.com/kevinburke/ssh_config	`v1.4.0`	indirect
Go	github.com/klauspost/cpuid/v2	`v2.3.0`	indirect
Go	github.com/mgutz/ansi	`v0.0.0-20200706080929-d51e80ef957d`	indirect
Go	github.com/microsoft/go-winio	`v0.6.2`	indirect
Go	github.com/pjbgf/sha1cd	`v0.6.0`	indirect
Go	github.com/pmezard/go-difflib	`v1.0.1-0.20181226105442-5d4384ee4fb2`	indirect
Go	github.com/protonmail/go-crypto	`v1.3.0`	indirect
Go	github.com/russross/blackfriday/v2	`v2.1.0`	indirect
Go	github.com/sergi/go-diff	`v1.4.0`	indirect
Go	github.com/skeema/knownhosts	`v1.3.2`	indirect
Go	github.com/stretchr/objx	`v0.5.3`	indirect
Go	github.com/xanzy/ssh-agent	`v0.3.3`	indirect
Go	github.com/xrash/smetrics	`v0.0.0-20250705151800-55b8f293f342`	indirect
Go	golang.org/x/net	`v0.56.0`	indirect
Go	golang.org/x/term	`v0.45.0`	indirect
Go	gopkg.in/warnings.v0	`v0.1.2`	indirect
Go	gopkg.in/yaml.v3	`v3.0.1`	indirect

Dependency advisories 1

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

Package	Version	Relation	Severity	Advisories	Fixed in
github.com/go-git/go-git/v5	`v5.19.1`	direct	high	4	`6.0.0-alpha.5`

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.

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 — Go.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records