Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-14 07:54 UTC

Heyosseus / vacuum

PostgreSQL health and performance advisor for Laravel. Detect bloat, vacuum debt, and slow queries with an interactive dashboard, automated CI gate, and optional Filament panel.

PHP · BladeMIT★ 3 stars⑂ 2 forkssince Jul 2026View on GitHub ↗
KindLibraryWeb interfacehow this is determined

Heyosseus/vacuum holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (68/100) and lowest on Community & Adoption (38/100). It was last updated today. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

RatiRukhadzePersonal account
21 followers46 public repossince Apr 2022

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistheyosseus/vacuumv1.0.12,954821 days agodatabaseperformancepostgresqlmonitoringpostgreslaraveldashboardvacuumobservabilityautovacuum

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
1.4/36Commit cadence2/52 weeks with commits
17.9/18Commit volume97 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year97
human_commit_share0.969
days_since_last_push0
active_weeks_last_year2
How it's scored
16.2/27Ships releases8 version tags (no GitHub releases)
36/36Release recencylatest release 21 days ago
27/27Release cadencea release every ~1.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv1.0.1
releases_from_tagsyes
days_since_latest_release21
mean_days_between_releases1.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?

38Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
46.3/80Monthly downloads2,954 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesheyosseus/vacuum
dependents0
ecosystemspackagist
total_downloads2,954
monthly_downloads2,954
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.1/22.5Commit distributiontop contributor authored 82% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.818
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance18/18 decided PRs merged
13/13Newcomer PR acceptance16/16 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/7 approved changesets -- score normalized to 1
Inputs used
merged_prs18
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d16
prs_decided_30d16
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d3
first_time_prs_merged_30d16
first_time_prs_decided_30d16
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
9.7/25Owner reach21 followers of Heyosseus
20.9/25Track record46 public repos, account ~4 yr old
Inputs used
followers21
owner_typeUser
is_verified
owner_loginHeyosseus
public_repos46
account_age_days1,592
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 21 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesheyosseus/vacuum
ecosystemspackagist
any_deprecatedno
min_days_since_publish21

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsdatabase-monitoring, database-performance, filamentphp, laravel, postgresql
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 1/7 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history91 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.968
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile
2.1/10Demonstrated agent practice1 of the last 97 commits agent-authored or agent-credited
8/8Automated maintenance2 of the last 97 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.021
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/362 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes23,240
source_files_sampled362
oversized_source_files0

Key facts

3GitHub stars
3contributors
97commits, last 12 months
0days since last push
8releases
1bus factor
0open issues
Packagistpackage ecosystems

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

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
3Releases

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.

111222212026-072026-072026-07
Major 0Minor 3Patch 0
OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-08-14 07:54 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
5CI-Tests4 out of 8 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/7 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistilluminate/console^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/contracts^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/database^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/routing^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/support^11.0 || ^12.0 || ^13.0composer.json
Packagistilluminate/view^11.0 || ^12.0 || ^13.0composer.json
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.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.