ranetrace/ranetrace-php

Project backingcaution

The registry namespace and repository owner match, supporting package ownership, but the owner is a user account rather than an organization, so there is limited institutional backing to offset contributor concentration.

Repo bus factorcaution

One contributor made 32 of 35 recent commits, or about 91%, leaving little demonstrated continuity if that contributor stops. The second active contributor partly offsets this but does not remove the concentration risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected, leaving a repository hygiene gap for a package that handles application and browser-captured data.

Security policycaution

The repository has no security policy, so there is no documented reporting path for vulnerabilities. This lowers transparency but is not evidence of a vulnerability.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both of its two action references are unpinned, which weakens build reproducibility.