Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 13:03 UTC

spiral-packages / scheduler

The scheduler is a package for spiral framework. It will help to managing scheduled tasks on your server.

PHPMIT★ 6 stars⑂ 3 forkssince Jan 2022View on GitHub ↗

spiral-packages/scheduler holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (73/100) and lowest on Security (34/100). It was last updated 61 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

34
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). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

21 followers24 public repossince Jan 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistspiral-packages/scheduler2.8.0110,4731461 days agoschedulerspiralspiral-packages

Metrics by category

Vitality

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

55Moderate · 21% of overall
How it's scored
18/36Push recencylast push 61 days ago
2.1/36Commit cadence3/52 weeks with commits
7.6/18Commit volume6 commits in the last year
2/10OpenSSF Scorecard: Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year6
human_commit_share0.897
days_since_last_push61
active_weeks_last_year3
How it's scored
27/27Ships releases14 releases published
36/36Release recencylatest release 61 days ago
19.8/27Release cadencea release every ~71 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tag2.8.0
releases_from_tagsno
days_since_latest_release61
mean_days_between_releases71
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?

40Weak · 17% of overall
How it's scored
11.3/60Stars6 stars
2.5/25Forks3 forks
0/15Watchers2 watchers
Inputs used
forks3
stars6
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
67.2/80Monthly downloads110,473 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesspiral-packages/scheduler
dependents0
ecosystemspackagist
total_downloads1,852,211
monthly_downloads110,473
unverified_packages_excluded

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.8/22.5Commit distributiontop contributor authored 70% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 28 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.697
How it's scored
42/42Issue resolution100% of issues closed
28.8/30PR acceptance24/25 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 7/11 approved changesets -- score normalized to 6
Inputs used
merged_prs24
open_issues0
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
9.7/25Owner reach21 followers of spiral-packages
19.2/25Track record24 public repos, account ~4 yr old
Inputs used
followers21
owner_typeOrganization
is_verified
owner_loginspiral-packages
public_repos24
account_age_days1,648
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 61 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspiral-packages/scheduler
ecosystemspackagist
any_deprecatedno
min_days_since_publish61

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests2 out of 12 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://spiral.dev/docs/advanced-scheduler
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsphp, php8, spiral-framework, package, cron, scheduler
has_wikiyes
homepagehttps://spiral.dev/docs/advanced-scheduler
docs_sitehttps://spiral.dev/docs/advanced-scheduler
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.2/2.5CI-Tests2 out of 12 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 7/11 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 28 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.8
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier36
security_posture_before_jurisdiction48
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20.6/40Legible commit history27 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.386
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php
0/11Static type checking
0/10Reproducible environment
5.1/10Demonstrated agent practice2 of the last 78 commits agent-authored or agent-credited
8/8Automated maintenance8 of the last 78 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.026
toolchain_manifests
dependency_bot_commit_share0.103
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/60 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes8,456
source_files_sampled60
oversized_source_files0

Key facts

6GitHub stars
5contributors
6commits, last 12 months
61days since last push
14releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

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

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.

12233312022-122024-022025-05
Major 0Minor 3Patch 2

Each point covers 3 days.

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-04 13:03 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
1CI-Tests2 out of 12 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 7/11 approved changesets -- score normalized to 6
10Contributorsproject has 28 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Packagistbutschster/cron-expression-generator^1.10composer.json
Packagistnesbot/carbon^2.52 || ^3.0 || ^4.0composer.json
Packagistpsr/event-dispatcher^1composer.json
Packagistspiral/core^3.14composer.json
Packagistspiral/boot^3.14composer.json
Packagistspiral/cache^3.14composer.json
Packagistspiral/queue^3.14composer.json
Packagistspiral/snapshots^3.14composer.json
Packagistspiral/attributes^2.8 || ^3.0composer.json
Packagistsymfony/process^6.0 || ^7.0 || ^8.0composer.json
All dependencies 16

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

RegistryPackageVersionRelation
Packagistbutschster/cron-expression-generatordirect
Packagistnesbot/carbondirect
Packagistpsr/event-dispatcherdirect
Packagistspiral/attributesdirect
Packagistspiral/bootdirect
Packagistspiral/cachedirect
Packagistspiral/coredirect
Packagistspiral/queuedirect
Packagistspiral/snapshotsdirect
Packagistsymfony/processdirect
Packagistphpindirect
Packagistspiral/code-styleindirect
Packagistspiral/dumperindirect
Packagistspiral/frameworkindirect
Packagistspiral/testingindirect
Packagistvimeo/psalmindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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