Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 23:08 UTC

CybercentreCanada / assemblyline-base

Base components for Assemblyline 4 (Datastore, ODM, Filestore, Remote Datatypes, utils function, etc...)

PythonMIT★ 73 stars⑂ 42 forkssince Jan 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

CybercentreCanada/assemblyline-base holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (84/100) and lowest on AI Readiness (40/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

Canadian Centre for Cyber SecurityOrganization · verified domain
577 followers136 public repossince Oct 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIassemblyline4.7.4.1723,4962,6561 day agoassemblylineautomatedmalwareanalysisgccanadacse-cstcsecstcybercccs

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
33.2/36Commit cadence — 48/52 weeks with commits
18/18Commit volume — 246 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year246
human_commit_share—
days_since_last_push1
active_weeks_last_year48
How it's scored
27/27Ships releases — 100 releases published
0/36Release recency — latest release 1,006 days ago
19.8/27Release cadence — a release every ~89.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv4.4.1.dev335
releases_from_tagsno
days_since_latest_release1,006
mean_days_between_releases89.2
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?

61Moderate · 17% of overall
How it's scored
30.1/60Stars — 73 stars
13.4/25Forks — 42 forks
2.7/15Watchers — 4 watchers
Inputs used
forks42
stars73
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
58.3/80Monthly downloads — 23,496 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesassemblyline
dependents—
ecosystemspypi
total_downloads—
monthly_downloads23,496
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?

84Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.2/22.5Commit distribution — top contributor authored 37% of commits
13.5/13.5Contributor breadth — 31 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled31
top_contributor_share0.369
How it's scored
0/42Issue resolution — no issues or no data
28.3/30PR acceptance — 2,044/2,170 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 15/20 approved changesets -- score normalized to 7
Inputs used
merged_prs2,044
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs126
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
19.9/25Owner reach — 577 followers of CybercentreCanada
25/25Track record — 136 public repos, account ~6 yr old
Inputs used
followers577
owner_typeOrganization
is_verifiedyes
owner_loginCybercentreCanada
public_repos136
account_age_days2,531

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 15 out of 16 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://cybercentrecanada.github.io/assemblyline4_docs/
10/10Repository description
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsassemblyline, malware-analysis
has_wikino
homepagehttps://cybercentrecanada.github.io/assemblyline4_docs/
docs_sitehttps://cybercentrecanada.github.io/assemblyline4_docs/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 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 — 15 out of 16 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
5.2/7.5Code-Review — Found 15/20 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
25.5/35Direct dependencies free of known advisories — 1 affected: paramiko 3.5.1 (low 3.4)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
36.9/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 122 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages72
unassessed_packages0
affected_by_severitylow 1
direct_affected_packages1
Matched the pypi:assemblyline@4.7.4.17 runtime dependency closure — what installing the published package pulls in — 72 packages. 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
0/11Lint / format config
11/11Static type checking — assemblyline/py.typed
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsassemblyline/py.typed
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable code — Python with type-check config (assemblyline/py.typed)
53.8/55Manageable file sizes — 4/191 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes3,003,115
source_files_sampled191
oversized_source_files4

Key facts

73GitHub stars
31contributors
246commits, last 12 months
1days since last push
100releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • GraphQL snapshot failed, fell back to REST: GitHub GraphQL error: Something went wrong while executing your query on 2026-09-05T23:06:50Z. Please include `99F2:3F3A69:B05AABD:AA5509F:6A9CA088` when reporting this issue.
  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 42 ⇿
0Stars
42Forks
100Releases

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.

010203040504222020-042023-062026-08
Major 0Minor 0Patch 0

Each point covers 6 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-05 23:07 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-Tests15 out of 16 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 15/20 approved changesets -- score normalized to 7
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities11 existing vulnerabilities detected
All dependencies 36

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

RegistryPackageVersionRelation
PyPIaiohttp—indirect
PyPIapscheduler—indirect
PyPIarrow—indirect
PyPIassemblyline-toolbox—indirect
PyPIazure-identity—indirect
PyPIazure-storage-blob—indirect
PyPIbcrypt—indirect
PyPIboto3—indirect
PyPIcart—indirect
PyPIchardet—indirect
PyPIelastic-apm—indirect
PyPIelasticsearch—indirect
PyPIhauntedhouse0.1.10indirect
PyPIlark—indirect
PyPImagika—indirect
PyPImsoffcrypto-tool—indirect
PyPInotifications-python-client—indirect
PyPIpackaging—indirect
PyPIparamiko—indirect
PyPIpyftpdlib—indirect
PyPIpyopenssl23.3.0indirect
PyPIpysftp—indirect
PyPIpytest—indirect
PyPIpytest-mock—indirect
PyPIpython-baseconv—indirect
PyPIpython-datemath—indirect
PyPIpython-magic—indirect
PyPIpytz—indirect
PyPIpyyaml—indirect
PyPIredis—indirect
PyPIrequests—indirect
PyPIretrying—indirect
PyPIrstr—indirect
PyPIurllib3—indirect
PyPIwebsocket-client—indirect
PyPIyara-python—indirect
Dependency advisories 1

Installing pypi:assemblyline@4.7.4.17 pulls in 72 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
paramiko3.5.1directlow2—

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.