Public recordWeak
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 11:58 UTC
shekhu10 / mailblastr-sdks
shekhu10/mailblastr-sdks holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Vitality (70/100) and lowest on Community & Adoption (23/100). It was last updated today. A single contributor accounts for most of its recent work.
42
overall / 100Software 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.
42
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)
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 45 is calibrated to 42 on the published index scale (record calibration 2026-08-02).
Ownership
shekhar bhardwajPersonal account
5 followers8 public repossince Jul 2017
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| Go | github.com/shekhu10/mailblastr-sdks/mailblastr-go/v5 | v5.0.1 | - | 2 | 8 days ago | — |
| Maven | com.mailblastr:mailblastr | 5.0.1 | - | 10 | 8 days ago | — |
| crates.io | mailblastr | 5.0.1 | 61 | 10 | 8 days ago | apiemailmailblastrsdktransactionalapi-bindings |
| npm | mailblastr-cli | 5.0.1 | 932 | 10 | 8 days ago | mailblastremailcliapitransactional |
| npm | mailblastr | 5.0.1 | 1,048 | 10 | 8 days ago | mailblastremailapitransactionalsesbroadcastaudience |
| Packagist | mailblastr/mailblastrpoints to another repo — not scored | v5.0.1 | 3 | 10 | 8 days ago | apiemailsdkmarketingtransactionalmailblastr |
| PyPI | mailblastr | 5.0.1 | 720 | 10 | 8 days ago | mailblastremailtransactionalmarketingsmtp |
| RubyGems | mailblastrpoints to another repo — not scored | 5.0.1 | - | 10 | 8 days ago | — |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
70
Development activity
58Moderate
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 6.2/36 | Commit cadence — 9/52 weeks with commits |
| 15.7/18 | Commit volume — 55 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully |
Inputs used
| commits_last_year | 55 |
| human_commit_share | 1 |
| days_since_last_push | 0 |
| active_weeks_last_year | 9 |
Release discipline
88Excellent
How it's scored
| 16.2/27 | Ships releases — 10 version tags (no GitHub releases) |
| 36/36 | Release recency — latest release 8 days ago |
| 27/27 | Release cadence — a release every ~3 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 10 |
| latest_release_tag | v5.0.1 |
| releases_from_tags | yes |
| days_since_latest_release | 8 |
| mean_days_between_releases | 3 |
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?
23
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
25At Risk
How it's scored
| 22.5/22.5 | README |
| 0/22.5 | License — no license file detected |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | no |
| readme_badges | 0 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
57Moderate
How it's scored
| 45.9/80 | Monthly downloads — 2,761 downloads/month across crates, go, maven, npm, pypi |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | github.com/shekhu10/mailblastr-sdks/mailblastr-go/v5, com.mailblastr:mailblastr, mailblastr, mailblastr-cli, mailblastr, mailblastr |
| dependents | — |
| ecosystems | crates, go, maven, npm, pypi |
| total_downloads | 184 |
| monthly_downloads | 2,761 |
| 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?
34
Maintainer resilience (bus factor)
10Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
Issue & PR responsiveness
1Critical
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 0/30 | PR acceptance — no decided pull requests or no data |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 0 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
43Weak
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 5.6/25 | Owner reach — 5 followers of shekhu10 |
| 18.9/25 | Track record — 8 public repos, account ~9 yr old |
Inputs used
| followers | 5 |
| owner_type | User |
| is_verified | — |
| owner_login | shekhu10 |
| public_repos | 8 |
| account_age_days | 3,331 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 6 package(s) on crates, go, maven, npm, pypi |
| 35/35 | Publish recency — latest publish 8 days ago |
| 20/20 | Version history — 10 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/shekhu10/mailblastr-sdks/mailblastr-go/v5, com.mailblastr:mailblastr, mailblastr, mailblastr-cli, mailblastr, mailblastr |
| ecosystems | crates, go, maven, npm, pypi |
| any_deprecated | no |
| min_days_since_publish | 8 |
Engineering Quality
Are baseline engineering and documentation practices in place?
58
Engineering practices
60Moderate
How it's scored
| 24/24 | CI workflows — 2 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
Documentation
55Moderate
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://www.mailblastr.com/docs |
| 0/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| docs_site | https://www.mailblastr.com/docs |
| has_readme | yes |
| has_docs_dir | no |
| has_description | no |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
32
Security posture
32At Risk
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 0/2.5 | Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 0/2.5 | License — license file not detected |
| 0/7.5 | Maintained — project was created within the last 90 days. Please review its contents carefully |
| 5/5 | Packaging — packaging workflow detected |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — no SAST tool detected |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 3.2 |
Excluded from scoring (no data or not applicable): CI-Tests, 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.
63
Agent context & guidance
55Moderate
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.mailblastr.com/llms.txt) |
| 40/40 | Legible commit history — 53 of 55 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | https://www.mailblastr.com/llms.txt |
| legible_history_share | 0.964 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
56Moderate
How it's scored
| 12.6/18 | One-command bootstrap — mailblastr-dotnet/src/Mailblastr/Mailblastr.csproj, mailblastr-dotnet/tests/Mailblastr.Tests/Mailblastr.Tests.csproj, mailblastr-go/go.mod (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — mailblastr-npm/tsconfig.json |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 55 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | mailblastr-npm/tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | mailblastr-dotnet/src/Mailblastr/Mailblastr.csproj, mailblastr-dotnet/tests/Mailblastr.Tests/Mailblastr.Tests.csproj, mailblastr-go/go.mod, mailblastr-java/pom.xml, mailblastr-rust/Cargo.toml |
| dependency_bot_commit_share | 0 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Rust (statically typed) |
| 54.6/55 | Manageable file sizes — 2/290 source files over 60KB |
Inputs used
| primary_language | Rust |
| largest_source_bytes | 65,592 |
| source_files_sampled | 290 |
| oversized_source_files | 2 |
Key facts
0GitHub stars
1contributors
55commits, last 12 months
0days since last push
10releases
1bus factor
0open issues
crates.io, Go, Maven, npm, Packagist, PyPIpackage ecosystems
Data collection warnings
- packagist package 'mailblastr/mailblastr' points at a different repository (https://github.com/shekhu10/mailblastr-php); excluded from ecosystem scoring
- rubygems package 'mailblastr' points at a different repository (https://www.mailblastr.com); excluded from ecosystem scoring
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 3.2 / 10
3.2aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 0 | Contributors | project has 0 contributing companies or organizations -- score normalized to 0 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 0 | License | license file not detected |
| 0 | Maintained | project was created within the last 90 days. Please review its contents carefully |
| 10 | Packaging | packaging workflow detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | no SAST tool detected |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 10
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | commander | ^12.1.0 | mailblastr-cli/package.json |
| npm | mailblastr | ^5.1.0 | mailblastr-cli/package.json |
| crates.io | reqwest | 0.12 | mailblastr-rust/Cargo.toml |
| crates.io | serde | 1 | mailblastr-rust/Cargo.toml |
| crates.io | serde_json | 1 | mailblastr-rust/Cargo.toml |
| crates.io | hmac | 0.12 | mailblastr-rust/Cargo.toml |
| crates.io | sha2 | 0.10 | mailblastr-rust/Cargo.toml |
| crates.io | base64 | 0.22 | mailblastr-rust/Cargo.toml |
| crates.io | tokio | 1 | mailblastr-rust/Cargo.toml |
| crates.io | httpdate | 1 | mailblastr-rust/Cargo.toml |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
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.
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 — Go, Maven, crates.io, npm, Packagist, PyPI, RubyGems.