neazk/blade-tabler-icons

Clear licensing, repository alignment, and release notes support transparency. The small release history, no commits in three months, missing security policy, and weak workflow pinning reduce confidence in long-term maintenance.

Latest 3.41

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases have been published, both on the same day, leaving limited evidence of an established release track despite the package being about 190 days old.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, which is a meaningful maintenance concern for a package that may need updates with its ecosystem.

Repo tooling

Composer is used for builds, but no security-scanning tooling is reported, leaving a modest transparency and hygiene gap.

Security policy

The repository has no security policy, so its process for receiving and handling vulnerability reports is not documented.

Workflow audit

All nine analyzed action references are unpinned, weakening build reproducibility. Two workflows grant top-level write permissions, but there are no untrusted checkouts, injection findings, or high-confidence audit findings.