Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-24 07:37 UTC

NepipenkoIgor / ngx-mask

Angular Plugin to make masks on form fields and html elements.

TypeScriptMIT★ 1,242 stars⑂ 307 forkssince Sep 2016View on GitHub ↗
KindWeb interfacehow this is determined

NepipenkoIgor/ngx-mask holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (91/100) and lowest on AI Readiness (66/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

Igor NepipenkoPersonal account
110 followers150 public repossince May 2014

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
npmngx-mask22.2.51,782,3522735 days agong2-maskngx-maskng2angular-maskmaskangularangular2angular2-maskng2mask

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
4.8/36Commit cadence — 7/52 weeks with commits
18/18Commit volume — 128 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year128
human_commit_share0.98
days_since_last_push1
active_weeks_last_year7

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 83 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~2.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count83
latest_release_tagv22.2.5
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases2.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?

91Excellent · 17% of overall
How it's scored
50.2/60Stars — 1,242 stars
20.7/25Forks — 307 forks
6.7/15Watchers — 17 watchers
Inputs used
forks307
stars1,242
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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_badges9
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,782,352 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesngx-mask
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,782,352
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.1/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 85 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled85
top_contributor_share0.375
How it's scored
41.1/42Issue resolution — 98% of issues closed
23.4/30PR acceptance — 520/667 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/28 approved changesets -- score normalized to 0
Inputs used
merged_prs520
open_issues22
closed_issues1,035
prs_merged_7d7
prs_decided_7d7
prs_merged_30d28
prs_decided_30d28
issue_closed_ratio0.979
closed_unmerged_prs147
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.7/25Owner reach — 110 followers of NepipenkoIgor
25/25Track record — 150 public repos, account ~12 yr old
Inputs used
followers110
owner_typeUser
is_verified—
owner_loginNepipenkoIgor
public_repos150
account_age_days4,531
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 5 days ago
20/20Version history — 273 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesngx-mask
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

79Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 28 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://nepipenkoigor.github.io/ngx-mask/
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsangular, input-mask, typescript, web, ng, mask, ngx-mask, ngx, decimals, pipe, character, dot-separator, percent, sufix, decimals-enter, eparator, symbol, special-characters, mask-options, input
has_wikiyes
homepagehttps://nepipenkoigor.github.io/ngx-mask/
docs_sitehttps://nepipenkoigor.github.io/ngx-mask/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

74Good · 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.2/2.5CI-Tests — 28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/28 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 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.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
4.5/5SAST — SAST tool detected but not run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Branch-Protection, 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_packages45
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 45 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.

66Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 96 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.98
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.9/55Manageable file sizes — 3/151 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes107,141
source_files_sampled151
oversized_source_files3

Key facts

1,242GitHub stars
85contributors
128commits, last 12 months
1days since last push
83releases
2bus factor
22open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 307 ⇿
0Stars
307Forks
78Releases

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.

012525037530162017-022021-122026-09
Major 2Minor 29Patch 47

Each point covers 9 days.

OpenSSF Scorecard 6.8 / 10
6.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-10-24 07:36 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
9CI-Tests28 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/28 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
9SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npm@angular/common22.2.3package.json
npm@angular/compiler22.2.3package.json
npm@angular/core22.2.3package.json
npm@angular/forms22.2.3package.json
npm@angular/platform-browser22.2.3package.json
npm@angular/router22.2.3package.json
npmhighlight.js11.12.0package.json
npmngx-highlightjs14.0.1package.json
All dependencies 45

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

RegistryPackageVersionRelation
npm@angular/common22.2.3direct
npm@angular/compiler22.2.3direct
npm@angular/core22.2.3direct
npm@angular/forms22.2.3direct
npm@angular/platform-browser22.2.3direct
npm@angular/router22.2.3direct
npmhighlight.js11.12.0direct
npmngx-highlightjs14.0.1direct
npm@angular-eslint/builder22.6.0indirect
npm@angular/build22.2.3indirect
npm@angular/cli22.2.3indirect
npm@angular/compiler-cli22.2.3indirect
npm@angular/language-service22.2.3indirect
npm@commitlint/cli21.2.3indirect
npm@commitlint/config-conventional21.2.3indirect
npm@eslint/js10.0.1indirect
npm@eslint/json2.1.1indirect
npm@size-limit/file14.2.0indirect
npm@tailwindcss/postcss4.3.3indirect
npm@types/node26.6.5indirect
npm@vitest/browser-playwright5.0.5indirect
npmangular-eslint22.6.0indirect
npmbaseline-browser-mapping2.11.29indirect
npmbrowserslist4.29.3indirect
npmcaniuse-lite1.0.30001816indirect
npmeslint10.12.0indirect
npmglobals17.13.0indirect
npmjsdom30.1.3indirect
npmlint-staged17.6.0indirect
npmng-packagr22.2.4indirect
npmplaywright1.64.1indirect
npmpostcss8.5.30indirect
npmpostcss-scss4.0.9indirect
npmprettier3.9.10indirect
npmsimple-git-hooks2.14.0indirect
npmsize-limit14.2.0indirect
npmstylelint17.16.0indirect
npmstylelint-config-recommended-scss17.0.1indirect
npmstylelint-prettier5.0.3indirect
npmstylelint-scss7.3.0indirect
npmtailwindcss4.3.3indirect
npmtype-coverage2.30.4indirect
npmtypescript6.0.3indirect
npmtypescript-eslint8.71.2indirect
npmvitest5.0.5indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 45 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 — npm.