Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 18:52 UTC

hiennc24 / moleculer-action-constants

TypeScriptNo license detected★ 0 stars⑂ 0 forkssince Oct 2024View on GitHub ↗

hiennc24/moleculer-action-constants holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Vitality (72/100) and lowest on Engineering Quality (17/100). It was last updated 13 days ago. 2 contributors account for most of its recent work.

44
overall / 100
Weak

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.

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

Ownership

Hien NguyenPersonal account
7 followers34 public repossince Jun 2014NashTech

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@hiennc24/constant1.9.02,81831813 days agoaction-constant-projecttypescript

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
28.8/36Push recencylast push 13 days ago
26.3/36Commit cadence38/52 weeks with commits
18/18Commit volume189 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year189
human_commit_share1
days_since_last_push13
active_weeks_last_year38
How it's scored
16.2/27Ships releases5 version tags (no GitHub releases)
7.2/36Release recencylatest release 637 days ago
27/27Release cadencea release every ~8.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tag1.0.29
releases_from_tagsyes
days_since_latest_release637
mean_days_between_releases8.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?

24At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers2 watchers
Inputs used
forks0
stars0
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
46/80Monthly downloads2,818 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@hiennc24/constant
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,818
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
13/22.5Commit distributiontop contributor authored 42% of commits
13.5/13.5Contributor breadth12 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.422
How it's scored
0/42Issue resolutionno issues or no data
29.4/30PR acceptance105/107 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/13 approved changesets -- score normalized to 2
Inputs used
merged_prs105
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d6
prs_decided_30d6
issue_closed_ratio
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
6.5/25Owner reach7 followers of hiennc24
23.2/25Track record34 public repos, account ~12 yr old
Inputs used
followers7
owner_typeUser
is_verified
owner_loginhiennc24
public_repos34
account_age_days4,467
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 13 days ago
20/20Version history318 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@hiennc24/constant
ecosystemsnpm
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 8 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 3/13 approved changesets -- score normalized to 2
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
0/7.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories11
affected_packages5
assessed_packages56
unassessed_packages0
affected_by_severityhigh 4, moderate 1
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 56 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.

39Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.9/40Legible commit history73 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.73
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
36.7/55Manageable file sizes1/3 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes119,852
source_files_sampled3
oversized_source_files1

Key facts

0GitHub stars
12contributors
189commits, last 12 months
13days since last push
5releases
2bus factor
0open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 2.6 / 10
2.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-10 18:51 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 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 3/13 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities11 existing vulnerabilities detected
All dependencies 56

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

RegistryPackageVersionRelation
npm@cspotcode/source-map-support0.8.1indirect
npm@isaacs/cliui8.0.2indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.0indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@pkgjs/parseargs0.11.0indirect
npm@tsconfig/node101.0.11indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.4indirect
npmacorn8.13.0indirect
npmacorn-walk8.3.4indirect
npmansi-regex5.0.1indirect
npmansi-regex6.1.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmarg4.1.3indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion2.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcreate-require1.1.1indirect
npmcross-spawn7.0.3indirect
npmdiff4.0.2indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmforeground-child3.3.0indirect
npmglob10.4.5indirect
npmis-fullwidth-code-point3.0.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmlru-cache10.4.3indirect
npmmake-error1.3.6indirect
npmminimatch9.0.5indirect
npmminipass7.1.2indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmrimraf5.0.6indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstring-width-cjs4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-ansi-cjs6.0.1indirect
npmts-node10.9.2indirect
npmtypescript5.6.3indirect
npmv8-compile-cache-lib3.0.1indirect
npmwhich2.0.2indirect
npmwrap-ansi8.1.0indirect
npmwrap-ansi-cjs7.0.0indirect
npmyn3.1.1indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.0.1indirecthigh55.0.9
cross-spawn7.0.3indirecthigh17.0.5
glob10.4.5indirecthigh111.1.0
minimatch9.0.5indirecthigh310.2.3
diff4.0.2indirectmoderate18.0.3

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