yamez/umeng

Release historydanger

The package has only two releases, both published in April 2020, with no releases in roughly six years. This is strong evidence of abandonment risk for a maintained integration library.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and providing no evidence of current maintenance.

Package scaffoldingcaution

The artifact includes a useful README, but the repository has no tests or changelog. The README helps consumers integrate, while the missing validation and change history reduce maintenance transparency.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tooling is present. This is a modest hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency concern for a package handling push-service credentials.