slim/plates

Release historydanger

The latest release was published about 11 years ago, with no releases in the last 12 months. That long pause is a substantial abandonment concern, even though the package has a six-release history.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with its last push being about 11 years ago. This materially increases the risk that defects or compatibility problems will remain unaddressed.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no observed organizational backing to compensate for the single registry maintainer or prolonged inactivity.

Repo toolingcaution

The repository uses Composer, which fits the package ecosystem. No security scanning tools are present, a modest transparency and maintenance gap for a dependency that has otherwise seen no recent activity.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though the package's greater concern is its prolonged inactivity.