samlify

Repo commit activitydanger

No commits and no active maintainers were recorded in the last three months. This is a concrete recent-maintenance gap despite the recent registry release and repository push evidence.

Build provenancecaution

The release has no build attestation or trusted-publisher provenance, leaving publication origin less independently verifiable even though other repository signals are healthy.

Dependency profilecaution

Seven runtime dependencies, including XML, cryptography, and encryption components, create a meaningful dependency surface for a security-sensitive SAML library, though the profile is not unusually large.

Maintainerscaution

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so the small publishing base presents a real continuity risk.

Project backingcaution

The source repository is owned by a user account rather than an organization, providing less institutional backing for long-term maintenance.