Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-09 15:38 UTC

BC-SECURITY / Empire

Empire is a post-exploitation and adversary emulation framework that is used to aid Red Teams and Penetration Testers.

PowerShellBSD-3-Clause★ 5,322 stars⑂ 701 forkssince Aug 2019forkView on GitHub ↗
KindCommand-line toolNetwork serviceLibraryhow this is determined

BC-SECURITY/Empire holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (81/100) and lowest on Security (44/100). It was last updated 31 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

BC SecurityOrganization
1,069 followers58 public repossince Jul 2019

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?

81Excellent · 21% of overall
How it's scored
18/36Push recency — last push 31 days ago
28.4/36Commit cadence — 41/52 weeks with commits
18/18Commit volume — 358 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year358
human_commit_share0.92
days_since_last_push31
active_weeks_last_year41
How it's scored
27/27Ships releases — 97 releases published
36/36Release recency — latest release 31 days ago
19.8/27Release cadence — a release every ~52.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count97
latest_release_tagv7.0.2
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases52.8
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?

62Moderate · 17% of overall
How it's scored
60/60Stars — 5,322 stars
23.7/25Forks — 701 forks
11.2/15Watchers — 106 watchers
Inputs used
forks701
stars5,322
watchers106
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges8
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

78Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
16.5/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.268
How it's scored
39.8/42Issue resolution — 95% of issues closed
26.8/30PR acceptance — 351/393 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_prs351
open_issues23
closed_issues411
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.947
closed_unmerged_prs42
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
21.8/25Owner reach — 1,069 followers of BC-SECURITY
24.9/25Track record — 58 public repos, account ~7 yr old
Inputs used
followers1,069
owner_typeOrganization
is_verifiedno
owner_loginBC-SECURITY
public_repos58
account_age_days2,640

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

60Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://bc-security.gitbook.io/empire-wiki/
0/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsempire, c2, redteam-infrastructure, hacktoberfest
has_wikiyes
homepagehttps://bc-security.gitbook.io/empire-wiki/
docs_sitehttps://bc-security.gitbook.io/empire-wiki/
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

44Weak · 16% of overall
How it's scored
0/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 1 out of 1 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 11 contributing companies or organizations
0/10Dangerous-Workflow — dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
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 — 47 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
6.5/35Direct dependencies free of known advisories — 4 affected: pyjwt 2.13.0 (critical 9.1), urllib3 2.7.0 (high 7.5), cryptography 49.0.0 (moderate 5.9), +1 more
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories84
affected_packages10
assessed_packages81
unassessed_packages0
affected_by_severitycritical 3, high 1, moderate 4, unknown 2
direct_affected_packages4
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.

74Good · 4% of overall
How it's scored
45/45Agent instructions — docs/starkiller/agents.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://bc-security.gitbook.io/llms.txt)
40/40Legible commit history — 76 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://bc-security.gitbook.io/llms.txt
legible_history_share0.826
agent_instruction_filesdocs/starkiller/agents.md
agent_instruction_max_bytes4,294
How it's scored
12.6/18One-command bootstrap — empire/server/data/agent/gopire/go.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 38 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 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_testsyes
lockfilesgo.sum, poetry.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.38
toolchain_manifestsempire/server/data/agent/gopire/go.mod
dependency_bot_commit_share0.08
How it's scored
0/45Type-checkable code — PowerShell without a type-check config
54.6/55Manageable file sizes — 4/527 source files over 60KB
Inputs used
primary_languagePowerShell
largest_source_bytes321,560
source_files_sampled527
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

5,322GitHub stars
99contributors
358commits, last 12 months
31days since last push
97releases
2bus factor
23open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • Could not fetch pypi package 'empire-bc-security-fork' from its registry

More detail

Star and fork history 0 ★ / 701 ⇿
0Stars
701Forks
97Releases

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.

0125250375500625750701112019-082023-032026-10
Major 1Minor 15Patch 78

Each point covers 7 days.

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-09 15:37 UTC

0Binary-Artifactsbinaries present in source code
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-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 11 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
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
0Vulnerabilities47 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
PyPIurllib3^2.7.0pyproject.toml
PyPIrequests^2.34.2pyproject.toml
PyPImacholib^1.16.4pyproject.toml
PyPIzlib_wrapper^0.1.3pyproject.toml
PyPIjinja2^3.1.6pyproject.toml
PyPIpyparsing^3.3.2pyproject.toml
PyPIPyMySQL^1.2.0pyproject.toml
PyPISQLAlchemy^2.0.51pyproject.toml
PyPIalembic^1.18.5pyproject.toml
PyPIPyYAML^6.0.3pyproject.toml
PyPIcryptography^49.0.0pyproject.toml
PyPIfastapi^0.138.1pyproject.toml
PyPIuvicorn^0.49.0pyproject.toml
PyPIaiofiles^25.1.0pyproject.toml
PyPIpython-multipart^0.0.32pyproject.toml
PyPIpyjwt^2.13.0pyproject.toml
PyPIpython-socketio^5.16.3pyproject.toml
PyPIFlask^3.1.3pyproject.toml
PyPIclick^8.4.2pyproject.toml
PyPIwerkzeug^3.1.8pyproject.toml
PyPIpysecretsocks—pyproject.toml
PyPIdonut-shellcode—pyproject.toml
PyPIpython-obfuscator^0.0.2pyproject.toml
PyPIpyinstaller^6.21.0pyproject.toml
PyPIpackaging^26.2pyproject.toml
PyPInetaddr^1.3.0pyproject.toml
PyPIbcrypt^5.0.0pyproject.toml
PyPIpydantic-settings^2.14.2pyproject.toml
PyPIprettytable^3.18.0pyproject.toml
PyPIplatformdirs^4.10.0pyproject.toml
All dependencies 81

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

RegistryPackageVersionRelation
PyPIaiofiles25.1.0direct
PyPIalembic1.18.5direct
PyPIbcrypt5.0.0direct
PyPIclick8.4.2direct
PyPIcryptography49.0.0direct
PyPIfastapi0.138.1direct
PyPIflask3.1.3direct
PyPIjinja23.1.6direct
PyPImacholib1.16.4direct
PyPInetaddr1.3.0direct
PyPIpackaging26.2direct
PyPIplatformdirs4.10.0direct
PyPIprettytable3.18.0direct
PyPIpydantic-settings2.14.2direct
PyPIpyinstaller6.21.0direct
PyPIpyjwt2.13.0direct
PyPIpymysql1.2.0direct
PyPIpyparsing3.3.2direct
PyPIpython-multipart0.0.32direct
PyPIpython-obfuscator0.0.2direct
PyPIpython-socketio5.16.3direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPIsqlalchemy2.0.51direct
PyPIurllib32.7.0direct
PyPIuvicorn0.49.0direct
PyPIwerkzeug3.1.8direct
PyPIzlib-wrapper0.1.3direct
Gogithub.com/gonutz/w32/v2v2.11.1indirect
Gogithub.com/ne0nd0g/go-clrv1.0.3indirect
Gogithub.com/praetorian-inc/goffloaderv0.0.0-20240916162044-43d46b0da23dindirect
Gogithub.com/riscript/pecoffv0.0.0-20200923152459-a332238caa87indirect
Gogolang.org/x/cryptov0.39.0indirect
Gogolang.org/x/sysv0.33.0indirect
Gogolang.org/x/textv0.26.0indirect
PyPIaltgraph0.17.5indirect
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.14.1indirect
PyPIbidict0.23.1indirect
PyPIblinker1.9.0indirect
PyPIcertifi2026.6.17indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.3indirect
PyPIexecnet2.1.2indirect
PyPIgreenlet3.5.2indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIitsdangerous2.2.0indirect
PyPImako1.3.12indirect
PyPImarkupsafe3.0.3indirect
PyPIpefile2024.8.26indirect
PyPIpluggy1.6.0indirect
PyPIpyasyncore1.0.5indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpyinstaller-hooks-contrib2026.6indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-env1.6.0indirect
PyPIpytest-rerunfailures16.3indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpython-engineio4.13.3indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIregex2026.5.9indirect
PyPIruff0.15.20indirect
PyPIsetuptools82.0.1indirect
PyPIsimple-websocket1.1.0indirect
PyPIstarlette1.3.1indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIwcwidth0.8.1indirect
PyPIwsproto1.3.2indirect
Dependency advisories 10

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: 10 carry known advisories, of which 4 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
pyjwt2.13.0directcritical282.15.0
anyio4.14.1indirectcritical64.14.2
golang.org/x/cryptov0.39.0indirectcritical350.56.0
urllib32.7.0directhigh62.8.0
cryptography49.0.0directmoderate250.0.0
werkzeug3.1.8directmoderate13.1.9
mako1.3.12indirectmoderate11.4.2
setuptools82.0.1indirectmoderate283.0.0
golang.org/x/sysv0.33.0indirectunknown10.44.0
golang.org/x/textv0.26.0indirectunknown20.41.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.

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.