Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 19:36 UTC

step-security / secure-repo

Orchestrate GitHub Actions Security

Go · TypeScriptAGPL-3.0★ 331 stars⑂ 54 forkssince Oct 2021View on GitHub ↗

KindLibraryApplicationhow this is determined

#security #github-actions #workflow #actions #github #golang #supply-chain-security #security-tools

step-security/secure-repo holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on Community & Adoption (55/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

overall / 100

Excellent

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

Ownership

StepSecurityOrganization · verified domain

255 followers616 public repossince Aug 2021

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/step-security/secure-repo	v1.12.9	-	40	9 days ago

Metrics by category

Vitality

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

86Excellent · 21% of overall

Development activity

76Good

How it's scored

28.8/36	Push recency — last push 9 days ago
19.4/36	Commit cadence — 28/52 weeks with commits
18/18	Commit volume — 125 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	125
human_commit_share	1
days_since_last_push	9
active_weeks_last_year	28

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 41 releases published
36/36	Release recency — latest release 9 days ago
27/27	Release cadence — a release every ~16.2 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	41
latest_release_tag	v1.12.9
releases_from_tags	no
days_since_latest_release	9
mean_days_between_releases	16.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?

55Moderate · 17% of overall

Popularity & adoption

59Moderate

How it's scored

40.9/60	Stars — 331 stars
14.4/25	Forks — 54 forks
3.3/15	Watchers — 5 watchers

Inputs used

forks	54
stars	331
watchers	5
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (AGPL-3.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	api.securityscorecards.dev, codecov.io, 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?

76Good · 23% of overall

Maintainer resilience (bus factor)

43Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
10.6/22.5	Commit distribution — top contributor authored 53% of commits
13.5/13.5	Contributor breadth — 19 contributors
10/10	OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10

Inputs used

bus_factor	1
contributors_sampled	19
top_contributor_share	0.531

Issue & PR responsiveness

83Excellent

How it's scored

39.5/42	Issue resolution — 94% of issues closed
19.2/30	PR acceptance — 629/981 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15	OpenSSF Scorecard: Code-Review — Found 9/10 approved changesets -- score normalized to 9

Inputs used

merged_prs	629
open_issues	70
closed_issues	1,095
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	8
prs_decided_30d	8
issue_closed_ratio	0.94
closed_unmerged_prs	352
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

90Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
17.3/25	Owner reach — 255 followers of step-security
23.2/25	Track record — 616 public repos, account ~5 yr old

Inputs used

followers	255
owner_type	Organization
is_verified	yes
owner_login	step-security
public_repos	616
account_age_days	1,866

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	github.com/step-security/secure-repo
ecosystems	go
any_deprecated	no
min_days_since_publish	9

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall

Engineering practices

68Good

How it's scored

24/24	CI workflows — 8 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 9 out of 9 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	no
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://app.stepsecurity.io
10/10	Repository description
10/10	Topics — 8 topics
10/10	Wiki

Inputs used

topics	security, github-actions, workflow, actions, github, golang, supply-chain-security, security-tools
has_wiki	yes
homepage	https://app.stepsecurity.io
docs_site	https://app.stepsecurity.io
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?

70Good · 16% of overall

Security posture

80Excellent

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
6/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5	CI-Tests — 9 out of 9 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
6.8/7.5	Code-Review — Found 9/10 approved changesets -- score normalized to 9
2.5/2.5	Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
7.5/7.5	Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
2.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
5/5	SAST — SAST tool is run on all commits
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5	Vulnerabilities — 114 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	8

Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

30At Risk

How it's scored

5.2/35	Direct dependencies free of known advisories — 8 affected: axios 0.26.0 (high 8.6), github.com/golang-jwt/jwt 3.2.2+incompatible (high 7.5), github.com/sirupsen/logrus 1.8.1 (high 7.5), +5 more
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
17.1/40	No advisories left outstanding — 8 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,680 days ago

Inputs used

source	osv
advisories	172
affected_packages	21
assessed_packages	81
unassessed_packages	0
affected_by_severity	critical 3, high 10, moderate 6, unknown 2
direct_affected_packages	8

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 81 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.

56Moderate · 4% of overall

Agent context & guidance

22At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
22.4/40	Legible commit history — 42 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.42
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

66Good

How it's scored

12.6/18	One-command bootstrap — go.mod (toolchain convention, no task runner)
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — Automate-PR/tsconfig.json, kbanalysis/tsconfig.json
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
5/8	Automated maintenance — dependency automation configured, none observed in the sampled commits
5/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5

Inputs used

has_nix	no
has_tests	yes
lockfiles	go.sum, package-lock.json
has_dockerfile	yes
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	Automate-PR/tsconfig.json, kbanalysis/tsconfig.json
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0

Code legibility for models

99Exceptional

How it's scored

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

Inputs used

primary_language	Go
largest_source_bytes	169,971
source_files_sampled	51
oversized_source_files	1

Key facts

331GitHub stars

19contributors

125commits, last 12 months

9days since last push

41releases

1bus factor

70open issues

Go, npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Could not fetch npm package 'kbanalysis' from its registry
Could not fetch npm package 'automate-pr' from its registry

More detail

Star and fork history 0 ★ / 54 ⇿

0Stars

54Forks

36Releases

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 1Minor 12Patch 21

Each point covers 5 days.

OpenSSF Scorecard 8.0 / 10

8.0aggregate

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-19 19:36 UTC

10	Binary-Artifacts	no binaries found in the repo
8	Branch-Protection	branch protection is not maximal on development and all release branches
10	CI-Tests	9 out of 9 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
9	Code-Review	Found 9/10 approved changesets -- score normalized to 9
10	Contributors	project has 3 contributing companies or organizations -- score normalized to 10
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
10	Maintained	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
5	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 5
10	SAST	SAST tool is run on all commits
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
0	Vulnerabilities	114 existing vulnerabilities detected

Direct dependencies 23

Registry	Package	Version constraint	Manifest
npm	@actions/core	`^1.6.0`	Automate-PR/package.json
npm	@actions/github	`^5.0.0`	Automate-PR/package.json
npm	@types/axios	`^0.14.0`	Automate-PR/package.json
npm	axios	`^0.26.0`	Automate-PR/package.json
npm	bluebird	`^3.7.2`	Automate-PR/package.json
npm	octokat	`^0.8.0`	Automate-PR/package.json
Go	github.com/asottile/dockerfile	`v3.1.0+incompatible`	go.mod
Go	github.com/aws/aws-lambda-go	`v1.30.0`	go.mod
Go	github.com/aws/aws-sdk-go	`v1.43.45`	go.mod
Go	github.com/paulvollmer/dependabot-config-go	`v0.1.1`	go.mod
Go	github.com/sirupsen/logrus	`v1.8.1`	go.mod
Go	gopkg.in/yaml.v3	`v3.0.0-20210107192922-496545a6307b`	go.mod
Go	gotest.tools	`v2.2.0+incompatible`	go.mod
Go	github.com/PaesslerAG/gval	`v1.1.2`	go.mod
Go	github.com/generikvault/gvalstrings	`v0.0.0-20180926130504-471f38f0112a`	go.mod
Go	github.com/golang-jwt/jwt	`v3.2.2+incompatible`	go.mod
Go	github.com/google/go-containerregistry	`v0.8.0`	go.mod
Go	github.com/google/go-github/v40	`v40.0.0`	go.mod
Go	github.com/jarcoal/httpmock	`v1.4.0`	go.mod
Go	github.com/lestrrat-go/jwx	`v1.2.25`	go.mod
Go	golang.org/x/oauth2	`v0.0.0-20220411215720-9780585627b5`	go.mod
npm	@actions/core	`^1.6.0`	kbanalysis/package.json
npm	@actions/github	`^5.0.0`	kbanalysis/package.json

All dependencies 81

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

Registry	Package	Version	Relation
Go	github.com/asottile/dockerfile	`3.1.0+incompatible`	direct
Go	github.com/aws/aws-lambda-go	`1.30.0`	direct
Go	github.com/aws/aws-sdk-go	`1.43.45`	direct
Go	github.com/generikvault/gvalstrings	`0.0.0-20180926130504-471f38f0112a`	direct
Go	github.com/golang-jwt/jwt	`3.2.2+incompatible`	direct
Go	github.com/google/go-containerregistry	`0.8.0`	direct
Go	github.com/google/go-github/v40	`40.0.0`	direct
Go	github.com/jarcoal/httpmock	`1.4.0`	direct
Go	github.com/lestrrat-go/jwx	`1.2.25`	direct
Go	github.com/paesslerag/gval	`1.1.2`	direct
Go	github.com/paulvollmer/dependabot-config-go	`0.1.1`	direct
Go	github.com/sirupsen/logrus	`1.8.1`	direct
Go	golang.org/x/oauth2	`0.0.0-20220411215720-9780585627b5`	direct
Go	gopkg.in/yaml.v3	`3.0.0-20210107192922-496545a6307b`	direct
Go	gotest.tools	`2.2.0+incompatible`	direct
npm	@actions/core	`1.6.0`	direct
npm	@actions/github	`5.0.0`	direct
npm	@types/axios	`0.14.0`	direct
npm	axios	`0.26.0`	direct
npm	bluebird	`3.7.2`	direct
npm	octokat	`0.8.0`	direct
Go	github.com/containerd/typeurl	`1.0.2`	indirect
Go	github.com/decred/dcrd/dcrec/secp256k1/v4	`4.0.0-20210816181553-5444fa50b93d`	indirect
Go	github.com/docker/cli	`20.10.14+incompatible`	indirect
Go	github.com/docker/distribution	`2.8.1+incompatible`	indirect
Go	github.com/docker/docker	`20.10.14+incompatible`	indirect
Go	github.com/docker/docker-credential-helpers	`0.6.4`	indirect
Go	github.com/goccy/go-json	`0.9.7`	indirect
Go	github.com/gogo/protobuf	`1.3.2`	indirect
Go	github.com/golang/protobuf	`1.5.2`	indirect
Go	github.com/google/go-cmp	`0.5.7`	indirect
Go	github.com/google/go-querystring	`1.1.0`	indirect
Go	github.com/jmespath/go-jmespath	`0.4.0`	indirect
Go	github.com/lestrrat-go/backoff/v2	`2.0.8`	indirect
Go	github.com/lestrrat-go/blackmagic	`1.0.0`	indirect
Go	github.com/lestrrat-go/httpcc	`1.0.1`	indirect
Go	github.com/lestrrat-go/iter	`1.0.1`	indirect
Go	github.com/lestrrat-go/option	`1.0.0`	indirect
Go	github.com/mitchellh/go-homedir	`1.1.0`	indirect
Go	github.com/moby/buildkit	`0.10.3`	indirect
Go	github.com/opencontainers/go-digest	`1.0.0`	indirect
Go	github.com/opencontainers/image-spec	`1.0.3-0.20211202183452-c5a74bcca799`	indirect
Go	github.com/pkg/errors	`0.9.1`	indirect
Go	golang.org/x/crypto	`0.0.0-20220427172511-eb4f295cb31f`	indirect
Go	golang.org/x/net	`0.0.0-20220421235706-1d1ef9303861`	indirect
Go	golang.org/x/sync	`0.0.0-20210220032951-036812b2e83c`	indirect
Go	golang.org/x/sys	`0.0.0-20220422013727-9388b58f7150`	indirect
Go	google.golang.org/appengine	`1.6.7`	indirect
Go	google.golang.org/protobuf	`1.28.0`	indirect
Go	gopkg.in/yaml.v2	`2.4.0`	indirect
npm	@actions/http-client	`1.0.11`	indirect
npm	@octokit/auth-token	`2.5.0`	indirect
npm	@octokit/core	`3.5.1`	indirect
npm	@octokit/endpoint	`6.0.12`	indirect
npm	@octokit/graphql	`4.8.0`	indirect
npm	@octokit/openapi-types	`11.2.0`	indirect
npm	@octokit/plugin-paginate-rest	`2.17.0`	indirect
npm	@octokit/plugin-rest-endpoint-methods	`5.13.0`	indirect
npm	@octokit/request	`5.6.3`	indirect
npm	@octokit/request-error	`2.1.0`	indirect
npm	@octokit/types	`6.34.0`	indirect
npm	@types/node	`17.0.21`	indirect
npm	@vercel/ncc	`0.30.0`	indirect
npm	before-after-hook	`2.2.2`	indirect
npm	deprecation	`2.3.1`	indirect
npm	encoding	`0.1.13`	indirect
npm	follow-redirects	`1.14.9`	indirect
npm	iconv-lite	`0.6.3`	indirect
npm	is-plain-object	`5.0.0`	indirect
npm	lodash	`4.17.21`	indirect
npm	node-fetch	`2.6.7`	indirect
npm	once	`1.4.0`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	tr46	`0.0.3`	indirect
npm	tunnel	`0.0.6`	indirect
npm	typescript	`4.6.4`	indirect
npm	universal-user-agent	`6.0.0`	indirect
npm	webidl-conversions	`3.0.1`	indirect
npm	whatwg-url	`5.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	xmlhttprequest	`1.8.0`	indirect

Dependency advisories 21

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

Package	Version	Relation	Severity	Advisories	Fixed in
github.com/docker/docker	`20.10.14+incompatible`	indirect	critical	27	`28.0.0`
github.com/moby/buildkit	`0.10.3`	indirect	critical	17	`0.31.1`
golang.org/x/crypto	`0.0.0-20220427172511-eb4f295cb31f`	indirect	critical	42	`3.4.0`
axios	`0.26.0`	direct	high	23	`1.18.0`
github.com/golang-jwt/jwt	`3.2.2+incompatible`	direct	high	2	`5.2.2`
github.com/sirupsen/logrus	`1.8.1`	direct	high	2	`1.9.3`
golang.org/x/oauth2	`0.0.0-20220411215720-9780585627b5`	direct	high	2	`0.27.0`
gopkg.in/yaml.v3	`3.0.0-20210107192922-496545a6307b`	direct	high	2	`3.0.1`
github.com/docker/cli	`20.10.14+incompatible`	indirect	high	2	`29.2.0+incompatible`
github.com/docker/distribution	`2.8.1+incompatible`	indirect	high	1	`2.8.2-beta.1`
golang.org/x/net	`0.0.0-20220421235706-1d1ef9303861`	indirect	high	29	`12.0.2`
google.golang.org/protobuf	`1.28.0`	indirect	high	2	`1.33.0`
lodash	`4.17.21`	indirect	high	3	`4.18.0`
@actions/core	`1.6.0`	direct	moderate	1	`1.9.1`
github.com/lestrrat-go/jwx	`1.2.25`	direct	moderate	8	`2.0.21`
@octokit/plugin-paginate-rest	`2.17.0`	indirect	moderate	1	`11.4.1`
@octokit/request	`5.6.3`	indirect	moderate	1	`9.2.1`
@octokit/request-error	`2.1.0`	indirect	moderate	1	`6.1.7`
follow-redirects	`1.14.9`	indirect	moderate	3	`1.16.0`
github.com/aws/aws-sdk-go	`1.43.45`	direct	unknown	2	—
golang.org/x/sys	`0.0.0-20220422013727-9388b58f7150`	indirect	unknown	1	`0.44.0`

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