vierwd/typo3-smarty

The project has a clear license, useful documentation, and recent repository activity. Its small contributor base, absent security policy, stale registry releases, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.

Latest 10.2.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 54 releases over roughly 10 years, but it published no registry releases in the last 12 months and the latest release is more than two years old. Recent repository commits partly offset the abandonment concern but do not restore release cadence.

Repo bus factor

All six recent commits came from one contributor, leaving maintenance highly concentrated. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo tooling

The project uses Composer build tooling, but no security-scanning tool was detected. This is a modest transparency and assurance gap.

Security policy

The repository has no security policy, so there is no documented route for reporting vulnerabilities or explaining security response practices.

Workflow audit

The workflow audit completed cleanly with no injection or high-severity findings, but all three action references are unpinned. The workflow also lacks a top-level permissions block, which is acceptable on its own.