Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-13 04:22 UTC

pester / Pester

Pester is the ubiquitous test and mock framework for PowerShell.

PowerShellCustom license★ 3,381 stars⑂ 478 forkssince Jan 2011View on GitHub ↗

pester/Pester holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (93/100) and lowest on Engineering Quality (66/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

PesterOrganization
58 followers7 public repossince Sep 2012

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?

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
12.5/36Commit cadence — 18/52 weeks with commits
18/18Commit volume — 227 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year227
human_commit_share0.97
days_since_last_push0
active_weeks_last_year18

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 64 days ago
27/27Release cadence — a release every ~7.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag6.2.0
releases_from_tagsno
days_since_latest_release64
mean_days_between_releases7.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?

93Exceptional · 17% of overall
How it's scored
57.2/60Stars — 3,381 stars
22.3/25Forks — 478 forks
12.1/15Watchers — 149 watchers
Inputs used
forks478
stars3,381
watchers149
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

94Exceptional
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges15
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, opencollective.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.9/22.5Commit distribution — top contributor authored 43% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 25 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled98
top_contributor_share0.428
How it's scored
40.5/42Issue resolution — 96% of issues closed
24.9/30PR acceptance — 1,105/1,330 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/27 approved changesets -- score normalized to 0
Inputs used
merged_prs1,105
open_issues57
closed_issues1,555
prs_merged_7d18
prs_decided_7d18
prs_merged_30d18
prs_decided_30d18
issue_closed_ratio0.965
closed_unmerged_prs225
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.7/25Owner reach — 58 followers of pester
18.6/25Track record — 7 public repos, account ~14 yr old
Inputs used
followers58
owner_typeOrganization
is_verifiedno
owner_loginpester
public_repos7
account_age_days5,167

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 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
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://pester.dev/
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicspowershell, pester-tests, powershell-tests, assertions, mocking, mock, testing, tdd, bdd, tdd-framework, bdd-framework
has_wikiyes
homepagehttps://pester.dev/
docs_sitehttps://pester.dev/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

77Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/27 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 25 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
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
advisories0
affected_packages0
assessed_packages4
unassessed_packages0
affected_by_severitynone
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 4 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 96 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
agent_instruction_files.github/copilot-instructions.md, CLAUDE.md
agent_instruction_max_bytes4,568
How it's scored
12.6/18One-command bootstrap — src/csharp/Pester/Pester.csproj, src/csharp/PesterTests/PesterTests.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — devcontainer, lockfile
10/10Demonstrated agent practice — 20 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfilespackages.lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configno
typecheck_configs—
agent_commit_share0.2
toolchain_manifestssrc/csharp/Pester/Pester.csproj, src/csharp/PesterTests/PesterTests.csproj
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable code — PowerShell without a type-check config
55/55Manageable file sizes — 0/69 source files over 60KB
Inputs used
primary_languagePowerShell
largest_source_bytes17,336
source_files_sampled69
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

3,381GitHub stars
98contributors
227commits, last 12 months
0days since last push
100releases
2bus factor
57open issues
—package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 478 ⇿
0Stars
478Forks
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.

010020030040050047572011-042019-012026-10
Major 2Minor 18Patch 25

Each point covers 15 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-13 04:21 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/27 approved changesets -- score normalized to 0
10Contributorsproject has 25 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool is not run on all commits -- score normalized to 9
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
All dependencies 4

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

RegistryPackageVersionRelation
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.0indirect
NuGetMicrosoft.PowerShell.5.1.ReferenceAssemblies1.0.0indirect
NuGetSystem.Formats.Asn18.0.1indirect
NuGetSystem.Management.Automation7.4.0indirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.