Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 19:32 UTC

smarty-php / smarty

Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic.

PHPCustom license★ 2,348 stars⑂ 708 forkssince Oct 2014View on GitHub ↗

smarty-php/smarty holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (83/100) and lowest on Security (44/100). It was last updated 19 days ago. A single contributor accounts for most of its recent work.

81
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.

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

Ownership

71 followers6 public repossince Feb 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistsmarty/smartyv5.8.4909,7259924 days agotemplating

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
28.8/36Push recencylast push 19 days ago
9.7/36Commit cadence14/52 weeks with commits
15.1/18Commit volume47 commits in the last year
10/10OpenSSF Scorecard: Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year47
human_commit_share1
days_since_last_push19
active_weeks_last_year14

Release discipline

100Exceptional
How it's scored
27/27Ships releases76 releases published
36/36Release recencylatest release 24 days ago
27/27Release cadencea release every ~34.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count76
latest_release_tagv5.8.4
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases34.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?

83Excellent · 17% of overall
How it's scored
54.7/60Stars2,348 stars
23.7/25Forks708 forks
12.5/15Watchers180 watchers
Inputs used
forks708
stars2,348
watchers180
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
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
79.5/80Monthly downloads909,725 downloads/month across packagist
18.2/20Registry dependents530 packages depend on it
Inputs used
packagessmarty/smarty
dependents530
ecosystemspackagist
total_downloads42,452,813
monthly_downloads909,725
unverified_packages_excluded

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6/22.5Commit distributiontop contributor authored 74% of commits
13.5/13.5Contributor breadth69 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled69
top_contributor_share0.735
How it's scored
37.5/42Issue resolution89% of issues closed
18.3/30PR acceptance192/315 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/30 approved changesets -- score normalized to 1
Inputs used
merged_prs192
open_issues85
closed_issues705
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.892
closed_unmerged_prs123
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
13.4/25Owner reach71 followers of smarty-php
18.2/25Track record6 public repos, account ~13 yr old
Inputs used
followers71
owner_typeOrganization
is_verified
owner_loginsmarty-php
public_repos6
account_age_days4,915
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 24 days ago
20/20Version history99 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessmarty/smarty
ecosystemspackagist
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicssmarty, php
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 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
1.8/2.5CI-Tests6 out of 8 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 10 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
2/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): 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.

62Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
17.6/40Legible commit history33 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.33
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,615
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0
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
54.9/55Manageable file sizes1/373 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes142,309
source_files_sampled373
oversized_source_files1

Key facts

2,348GitHub stars
69contributors
47commits, last 12 months
19days since last push
76releases
1bus factor
85open issues
Packagist, PyPIpackage 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 ★ / 708 ⇿
0Stars
708Forks
76Releases

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.

0125250375500625750694162014-112020-092026-07
Major 2Minor 12Patch 59

Each point covers 11 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-07-23 19:32 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
7CI-Tests6 out of 8 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/30 approved changesets -- score normalized to 1
10Contributorsproject has 10 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained25 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistsymfony/polyfill-mbstring^1.27composer.json
All dependencies 9

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

RegistryPackageVersionRelation
Packagistsymfony/polyfill-mbstringdirect
Packagistphpindirect
Packagistphpunit/phpunitindirect
Packagistsmarty/smarty-lexerindirect
PyPImikeindirect
PyPImkdocsindirect
PyPImkdocs-materialindirect
PyPIpygmentsindirect
PyPIpymdown-extensionsindirect
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.27.0 — full methodology · metrics wiki.

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