Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-13 16:54 UTC

getbrevo / brevo-python

A fully-featured Python API client to interact with Brevo.

PythonNo license detected★ 35 stars⑂ 8 forkssince May 2023View on GitHub ↗

getbrevo/brevo-python holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Security (47/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

BrevoOrganization · verified domain
54 followers11 public repossince Apr 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIbrevo-python5.1.0256,073130 days agoapisdkclientbrevosendinbluetransactionalemailsmsmarketingautomation

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
14.6/18Commit volume — 41 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year41
human_commit_share0.642
days_since_last_push0
active_weeks_last_year8

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 14 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~26.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv5.1.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases26.1
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?

51Moderate · 17% of overall
How it's scored
24.8/60Stars — 35 stars
7/25Forks — 8 forks
0/15Watchers — 1 watchers
Inputs used
forks8
stars35
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
72.1/80Monthly downloads — 256,073 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbrevo-python
dependents—
ecosystemspypi
total_downloads—
monthly_downloads256,073
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6/22.5Commit distribution — top contributor authored 74% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.735
How it's scored
42/42Issue resolution — 100% of issues closed
21.6/30PR acceptance — 18/25 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs18
open_issues0
closed_issues18
prs_merged_7d2
prs_decided_7d4
prs_merged_30d2
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs7
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
12.5/25Owner reach — 54 followers of getbrevo
14.9/25Track record — 11 public repos, account ~3 yr old
Inputs used
followers54
owner_typeOrganization
is_verifiedyes
owner_logingetbrevo
public_repos11
account_age_days1,279

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 13 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbrevo-python
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
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://developers.brevo.com/
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsbrevo, client, crm, emailing-service, python
has_wikiyes
homepagehttps://developers.brevo.com/
docs_sitehttps://developers.brevo.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 14 out of 14 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
0/7.5Code-Review — Found 0/7 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Packaging, 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_packages40
unassessed_packages13
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 40 resolved dependencies against OSV. 13 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

61Moderate · 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 served by the project website (https://developers.brevo.com/llms.txt)
32.9/40Legible commit history — 21 of 34 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developers.brevo.com/llms.txt
legible_history_share0.618
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/brevo/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 3 of the last 53 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configssrc/brevo/py.typed
agent_commit_share0.057
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/brevo/py.typed)
53.8/55Manageable file sizes — 20/940 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes228,912
source_files_sampled940
oversized_source_files20

Key facts

35GitHub stars
2contributors
41commits, last 12 months
0days since last push
14releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:brevo-python@5.1.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 8 ⇿
0Stars
8Forks
10Releases

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.

02468812024-112025-102026-09
Major 0Minor 1Patch 7

Each point covers 2 days.

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-13 16:54 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/7 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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 6
RegistryPackageVersion constraintManifest
PyPIaiohttp>=3.14.1,<4pyproject.toml
PyPIhttpx>=0.21.2pyproject.toml
PyPIhttpx-aiohttp^0.1.8pyproject.toml
PyPIpydantic>= 1.9.2pyproject.toml
PyPIpydantic-core>=2.18.2,<3.0.0pyproject.toml
PyPItyping_extensions>= 4.0.0pyproject.toml
All dependencies 53

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

RegistryPackageVersionRelation
PyPIaiohttp3.14.5direct
PyPIhttpx—direct
PyPIhttpx0.28.1direct
PyPIhttpx-aiohttp0.1.12direct
PyPIpydantic—direct
PyPIpydantic2.14.1direct
PyPIpydantic-core—direct
PyPIpydantic-core2.50.1direct
PyPItyping-extensions—direct
PyPItyping-extensions4.16.0direct
PyPIaiohappyeyeballs2.7.1indirect
PyPIaiosignal1.4.0indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.1indirect
PyPIasync-timeout5.0.1indirect
PyPIattrs26.1.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIcertifi—indirect
PyPIcertifi2026.7.22indirect
PyPIcolorama0.4.6indirect
PyPIcoverage—indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecnet2.1.2indirect
PyPIfrozenlist1.8.0indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.1indirect
PyPImultidict7.1.0indirect
PyPImypy1.13.0indirect
PyPImypy-extensions1.1.0indirect
PyPInose—indirect
PyPIpackaging26.3indirect
PyPIpluggy—indirect
PyPIpluggy1.6.0indirect
PyPIpropcache0.5.4indirect
PyPIpy—indirect
PyPIpygments2.21.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil—indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIrandomize—indirect
PyPIruff0.11.5indirect
PyPIsix—indirect
PyPIsix1.17.0indirect
PyPItomli2.5.0indirect
PyPItypes-python-dateutil2.9.0.20260807indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib3—indirect
PyPIurllib32.8.0indirect
PyPIyarl1.25.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 40 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 13 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 — PyPI.