GoSign OneSign API client for PHP
65%
Total Score
50
94
50
The registry namespace and repository owner match, so the source appears connected to the published package. The owner is recorded as a user account rather than an organization, which provides limited backing evidence.
The package has five releases over about five years, but none in the last 12 months; the latest release was published about 19 months ago. This indicates slowing maintenance despite the recent version release.
There were no commits and no active maintainers in the last three months. Combined with no registry releases in the last 12 months, this is evidence of a substantial slowdown in maintenance.
The repository has no security policy or documented vulnerability-reporting process. For a library handling electronic-signature API interactions, this is a meaningful transparency gap.
Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all 16 analyzed action references are unpinned, leaving build inputs less reproducible and exposed to action changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/cache Version ^1.0 | — | — |
php-http/httplug Version ^2.2 | — | — |
psr/http-message Version ^1.0 | — | — |
php-http/discovery Version ^1.12 | — | — |
spatie/array-to-xml Version ^2.16 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.