jagdish-j-p/sbi-pay

Release historydanger

Only one release exists, published about 3 years ago, with no releases in the last 12 months. This substantially limits evidence of ongoing maintenance.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Combined with the single-release history, this raises maintenance and abandonment concerns.

Security policycaution

The repository has no published security policy. This is a transparency gap for a payment integration, though it is not severe enough to make the release unfit on its own.

Workflow auditcaution

Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all four action references are unpinned, leaving avoidable build-integrity risk.