vamshop/materializecss

The artifact has an MIT license, a README, and tests, and the repository matches the package under an organization account. Its small dependency set helps limit integration surface, but security documentation is absent.

Latest 3.0.13

Packagist

44%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package declares Composer lifecycle scripts that run during installation and project creation. Their presence warrants awareness because they execute package-provided behavior, but no evidence here shows that they are unsafe.

Release history

The package has only three releases, with the latest published in October 2018 and none in the following eight years. That long release gap is a substantial abandonment concern, although the package is not marked deprecated.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the prolonged release gap. This leaves little evidence of ongoing maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these numbers provide no meaningful community-maintenance signal.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package that ships application-facing assets.