vipertecpro/consent

App Tracking Transparency prompt and a cross-platform consent store (analytics, ads, personalisation) with events — native, hand-written, for NativePHP Mobile.

Latest v1.0.0

Packagist

62%

Total Score

caution

A first release with no observed commit activity yet and two unpinned workflow actions leaves maintenance and build-reproducibility concerns.

Health Score Breakdown

Maintainers

There is one registry publishing account. That is a modest resilience concern for a user-owned project, though the linked repository and registry namespace match.

Project backing

The registry namespace and repository owner match, but ownership is a single user account rather than an organization, so there is limited visible institutional backing.

Release history

This is the package's first release, published today, so there is no demonstrated release cadence or history yet. That is an early-maturity concern rather than evidence of abandonment.

Repo commit activity

No commits or active maintainers were observed during the last three months. Because the repository was created or updated today and this is the first release, the result may simply reflect its age, but maintenance capacity is not yet demonstrated.

Repo tooling

Composer is used for builds, but no security-scanning tool was detected. This is a minor transparency and hygiene gap, not a standalone supply-chain warning.