Veedubin / AttackLM
Security AI trainer/tuner and research toolkit. Fine-tune LLMs on MITRE ATT&CK-grounded data (QLoRA, GaLore, DeepSpeed, FP8, BitNet). 24K+ training pairs, 18 sources, 100% per-record provenance. Inversion-audit harness (Carlini 2021, 2022; MUSE 2024; LiRA). Terminal GUI for SSH use. 368+ tests.
Veedubin/AttackLM holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (72/100) and lowest on Community & Adoption (34/100). It was last updated 54 days ago. A single contributor accounts for most of its recent work.
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.
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 53 is calibrated to 54 on the published index scale (record calibration 2026-08-02).
Ownership
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 |
|---|---|---|---|---|---|---|
| PyPI | attacklm | 0.17.5 | 454 | 74 | 54 days ago | ai-securityfine-tuningmitre-attackoffensive-securityqlorared-teamsecurity |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 18/36 | Push recency — last push 54 days ago |
| 4.8/36 | Commit cadence — 7/52 weeks with commits |
| 18/18 | Commit volume — 170 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — no data |
Inputs used
| commits_last_year | 170 |
| human_commit_share | 1 |
| days_since_last_push | 54 |
| active_weeks_last_year | 7 |
Release discipline
How it's scored
| 27/27 | Ships releases — 33 releases published |
| 36/36 | Release recency — latest release 61 days ago |
| 27/27 | Release cadence — a release every ~1.1 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 33 |
| latest_release_tag | v0.13.0 |
| releases_from_tags | no |
| days_since_latest_release | 61 |
| mean_days_between_releases | 1.1 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 0/60 | Stars — 1 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 1 watchers |
Inputs used
| forks | 0 |
| stars | 1 |
| watchers | 1 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 16.9/22.5 | License — license file present, not a recognized license |
| 18/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 | yes |
| readme_badges | 5 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | shields.io |
| has_pull_request_template | no |
How it's scored
| 35.4/80 | Monthly downloads — 454 downloads/month across pypi |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | attacklm |
| dependents | — |
| ecosystems | pypi |
| total_downloads | — |
| monthly_downloads | 454 |
| unverified_packages_excluded | — |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.2/22.5 | Commit distribution — top contributor authored 99% of commits |
| 2.7/13.5 | Contributor breadth — 2 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — no data |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 2 |
| top_contributor_share | 0.992 |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 3.4/25 | Owner reach — 2 followers of Veedubin |
| 21.6/25 | Track record — 20 public repos, account ~10 yr old |
Inputs used
| followers | 2 |
| owner_type | User |
| is_verified | — |
| owner_login | Veedubin |
| public_repos | 20 |
| account_age_days | 3,872 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on pypi |
| 35/35 | Publish recency — latest publish 54 days ago |
| 20/20 | Version history — 74 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | attacklm |
| ecosystems | pypi |
| any_deprecated | no |
| min_days_since_publish | 54 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 3 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 |
Documentation
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://github.com/Veedubin/AttackLM#readme |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| docs_site | https://github.com/Veedubin/AttackLM#readme |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 0/30 | Security policy (SECURITY.md) |
| 0/25 | Dependabot config |
| 25/25 | Dependency lockfiles — uv.lock |
| 0/20 | CodeQL workflow |
Inputs used
| source | file_signals |
| lockfiles | uv.lock |
| manifests | pyproject.toml, requirements.txt |
| has_codeql_workflow | no |
| has_security_policy | no |
| has_dependabot_config | no |
Dependency advisories
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 0 |
| affected_packages | 0 |
| assessed_packages | 19 |
| unassessed_packages | 0 |
| affected_by_severity | none |
| direct_affected_packages | 0 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 94 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.94 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 18/18 | One-command bootstrap — Makefile |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — lockfile |
| 2/10 | Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | uv.lock |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | Makefile |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0.01 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — Python without a type-check config |
| 53.6/55 | Manageable file sizes — 2/78 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 239,318 |
| source_files_sampled | 78 |
| oversized_source_files | 2 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/10 17:30:05 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks
More detail
Direct dependencies 3
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | httpx | >=0.27 | pyproject.toml |
| PyPI | pydantic | >=2.0 | pyproject.toml |
| PyPI | textual | >=2.0 | pyproject.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
Dependency advisories 0
Installing pypi:attacklm@0.17.5 pulls in 19 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.
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.
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.