jinnguyen/puja-stdlib

Release historydanger

The package has only 3 releases, with none in the last 12 months; its latest release was about 9 years ago. This strongly indicates abandonment risk despite a historically regular 17-day median interval.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving no evidence of current maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tooling is present. This is a modest supply-chain hygiene gap, not evidence of maliciousness or immediate unfitness on its own.

Repository archivedcaution

The repository is not marked archived, which is a small positive, but its last push was about 9 years ago and does not offset the observed inactivity.

Security policycaution

The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a secondary concern beside the much larger maintenance gap.