ethanolivertroy / wilma
Wilma - AWS Bedrock Security Configuration Checker
ethanolivertroy/wilma holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Community & Adoption (39/100). It was last updated 2 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 67 is calibrated to 78 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 | wilma-sec | 1.1.0 | - | 3 | 259 days ago | awsbedrocksecuritygenaiaimlauditcompliancewilma |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 2 days ago |
| 7.6/36 | Commit cadence — 11/52 weeks with commits |
| 16.8/18 | Commit volume — 74 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 74 |
| human_commit_share | 0.865 |
| days_since_last_push | 2 |
| active_weeks_last_year | 11 |
Release discipline
How it's scored
| 27/27 | Ships releases — 2 releases published |
| 36/36 | Release recency — latest release 2 days ago |
| 27/27 | Release cadence — a release every ~3.7 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 2 |
| latest_release_tag | v0.2.2 |
| releases_from_tags | no |
| days_since_latest_release | 2 |
| mean_days_between_releases | 3.7 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 4.9/60 | Stars — 3 stars |
| 0/25 | Forks — 1 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 1 |
| stars | 3 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (GPL-3.0) |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | yes |
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 |
| 1.4/22.5 | Commit distribution — top contributor authored 94% of commits |
| 2.7/13.5 | Contributor breadth — 2 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 2 |
| top_contributor_share | 0.938 |
Issue & PR responsiveness
How it's scored
| 41.3/42 | Issue resolution — 98% of issues closed |
| 8.8/30 | PR acceptance — 17/58 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/10 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 17 |
| open_issues | 1 |
| closed_issues | 62 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.984 |
| closed_unmerged_prs | 41 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 16.9/25 | Owner reach — 220 followers of ethanolivertroy |
| 25/25 | Track record — 198 public repos, account ~6 yr old |
Inputs used
| followers | 220 |
| owner_type | User |
| is_verified | — |
| owner_login | ethanolivertroy |
| public_repos | 198 |
| account_age_days | 2,287 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on pypi |
| 26/35 | Publish recency — latest publish 259 days ago |
| 12/20 | Version history — 3 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | wilma-sec |
| ecosystems | pypi |
| any_deprecated | no |
| min_days_since_publish | 259 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 4 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config |
| 9.6/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | yes |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 5 topics |
| 10/10 | Wiki |
Inputs used
| topics | aws, bedrock, genai, llm, security |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/10 approved changesets -- score normalized to 0 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 2/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4 |
| 5/5 | SAST — SAST tool is run on all commits |
| 5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 7.5/7.5 | Token-Permissions — GitHub workflow tokens follow principle of least privilege |
| 6/7.5 | Vulnerabilities — 2 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 7.6 |
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 | 10 |
| 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
| 45/45 | Agent instructions — CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 57 of 64 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.891 |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 11,688 |
Verify loop (build / test / typecheck)
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config |
| 0/11 | Static type checking |
| 0/10 | Reproducible environment |
| 10/10 | Demonstrated agent practice — 20 of the last 74 commits agent-authored or agent-credited |
| 8/8 | Automated maintenance — 10 of the last 74 commits are automated dependency updates |
| 4/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0.27 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0.135 |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — Python without a type-check config |
| 50.9/55 | Manageable file sizes — 3/40 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 125,690 |
| source_files_sampled | 40 |
| oversized_source_files | 3 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
OpenSSF Scorecard 7.6 / 10
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 |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 15 out of 15 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/10 approved changesets -- score normalized to 0 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 4 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 4 |
| 10 | SAST | SAST tool is run on all commits |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 10 | Token-Permissions | GitHub workflow tokens follow principle of least privilege |
| 8 | Vulnerabilities | 2 existing vulnerabilities detected |
Direct dependencies 4
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | boto3 | >=1.43.51,<2.0.0 | pyproject.toml |
| PyPI | botocore | >=1.43.51,<2.0.0 | pyproject.toml |
| PyPI | rich | >=15.0.0,<16.0.0 | pyproject.toml |
| PyPI | pyyaml | >=6.0.3,<7.0.0 | pyproject.toml |
All dependencies 19
Full resolved dependency set from the GitHub dependency graph: 4 direct and 15 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| PyPI | boto3 | — | direct |
| PyPI | botocore | — | direct |
| PyPI | pyyaml | — | direct |
| PyPI | rich | — | direct |
| PyPI | bandit | — | indirect |
| PyPI | boto3-stubs | — | indirect |
| PyPI | build | — | indirect |
| PyPI | ipython | — | indirect |
| PyPI | moto | — | indirect |
| PyPI | mypy | — | indirect |
| PyPI | pre-commit | — | indirect |
| PyPI | pytest | — | indirect |
| PyPI | pytest-cov | — | indirect |
| PyPI | pytest-mock | — | indirect |
| PyPI | pytest-xdist | — | indirect |
| PyPI | ruff | — | indirect |
| PyPI | setuptools | — | indirect |
| PyPI | twine | — | indirect |
| PyPI | types-pyyaml | — | indirect |
Dependency advisories 0
Installing pypi:wilma-sec@1.1.0 pulls in 10 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.27.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — PyPI.