Public record
Software health reportschema 0.13.0 · metrics 2.10.0 · 2026-07-18 16:04 UTC

eggjs / security

Security plugin for egg, force performance too.

TypeScript · JavaScriptMIT★ 239 stars⑂ 41 forkssince Aug 2016View on GitHub ↗

eggjs/security holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (77/100) and lowest on Security (38/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

eggOrganization
229 followers186 public repossince Nov 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@eggjs/security4.0.210,707493 days agoeggeggpluginegg-pluginsecurity

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
0.7/36Commit cadence1/52 weeks with commits
4.3/18Commit volume2 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year2
human_commit_share
days_since_last_push3
active_weeks_last_year1
How it's scored
27/27Ships releases12 releases published
7.2/36Release recencylatest release 530 days ago
27/27Release cadencea release every ~43.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tagv4.0.1
releases_from_tagsno
days_since_latest_release530
mean_days_between_releases43.9
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?

57Moderate · 17% of overall
How it's scored
38.6/60Stars239 stars
13.4/25Forks41 forks
5.8/15Watchers12 watchers
Inputs used
forks41
stars239
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
53.7/80Monthly downloads10,707 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@eggjs/security
dependents
ecosystemsnpm
total_downloads
monthly_downloads10,707
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.5/22.5Commit distributiontop contributor authored 31% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 43 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled21
top_contributor_share0.312
How it's scored
22.9/42Issue resolution55% of issues closed
26.5/30PR acceptance83/94 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/30 approved changesets -- score normalized to 2
Inputs used
merged_prs83
open_issues5
closed_issues6
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.545
closed_unmerged_prs11
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
17/25Owner reach229 followers of eggjs
25/25Track record186 public repos, account ~10 yr old
Inputs used
followers229
owner_typeOrganization
is_verified
owner_logineggjs
public_repos186
account_age_days3,900
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 3 days ago
20/20Version history49 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@eggjs/security
ecosystemsnpm
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsegg-plugin, security, egg
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

38Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests1 out of 15 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 7/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 43 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/212 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes23,751
source_files_sampled212
oversized_source_files0

Key facts

239GitHub stars
21contributors
2commits, last 12 months
3days since last push
12releases
2bus factor
5open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-07-18 16:04 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
0CI-Tests1 out of 15 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/30 approved changesets -- score normalized to 2
10Contributorsproject has 43 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npm@eggjs/core^6.2.13package.json
npm@eggjs/ip^2.1.0package.json
npmcsrf^3.0.6package.json
npmegg-path-matching^2.1.0package.json
npmescape-html^1.0.3package.json
npmextend^3.0.1package.json
npmkoa-compose^4.1.0package.json
npmmatcher^4.0.0package.json
npmnanoid^3.3.8package.json
npmtype-is^1.6.18package.json
npmxss^1.0.3package.json
npmzod^3.24.1package.json
All dependencies 36

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

RegistryPackageVersionRelation
npm@eggjs/core^6.2.13direct
npm@eggjs/ip^2.1.0direct
npmcsrf^3.0.6direct
npmegg-path-matching^2.1.0direct
npmescape-html^1.0.3direct
npmextend^3.0.1direct
npmkoa-compose^4.1.0direct
npmmatcher^4.0.0direct
npmnanoid^3.3.8direct
npmtype-is^1.6.18direct
npmxss^1.0.3direct
npmzod^3.24.1direct
npm@arethetypeswrong/cli^0.17.1indirect
npm@eggjs/bin7indirect
npm@eggjs/mock^6.0.5indirect
npm@eggjs/supertest^8.2.0indirect
npm@eggjs/tsconfig1indirect
npm@types/escape-html^1.0.4indirect
npm@types/extend^3.0.4indirect
npm@types/koa-compose^3.2.8indirect
npm@types/mocha10indirect
npm@types/node22indirect
npm@types/type-is^1.6.7indirect
npmbeautify-benchmark^0.2.4indirect
npmbenchmark^2.1.4indirect
npmegg^4.0.4indirect
npmegg-view-nunjucks^2.3.0indirect
npmeslint8indirect
npmeslint-config-egg14indirect
npmrimraf6indirect
npmsnap-shot-it^7.9.10indirect
npmspy^1.0.0indirect
npmsupertest^6.3.3indirect
npmtshy3indirect
npmtshy-after1indirect
npmtypescript5indirect
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.13.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.