tualo/revenuecat

The matching repository and MIT license provide useful transparency, while the README is only 13 characters and no security policy is published. The organization-backed project has only one release, so sustained maintenance remains unproven.

Latest 1.0.1

Packagist

62%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package includes a README, but it is only 13 characters long and provides essentially no integration guidance. The absence of tests and a changelog is normal for published package artifacts and is not treated as a gap.

Release history

This package has only one release, published 444 days ago, with no releases in the last 12 months. That makes ongoing maintenance difficult to establish despite the repository being recently pushed.

Repo tooling

Composer is used as the build tool, which is appropriate for this package, but no security scanning tools are configured. The missing scanning reduces maintenance hygiene without outweighing the broader project evidence.

Security policy

The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is not evidence of a security defect by itself.