cyber-duck/pardot-api
The repository has no recent commits or issue activity, and the published license conflicts with the detected BSD-2-Clause license file. Documentation and organization backing provide useful transparency, but maintenance appears too stale for a low-risk dependency.
48%
Total Score
50
71
75
Health Score Breakdown
The package has only two releases, with the latest in January 2021 and none in the last 12 months. That long release gap is a meaningful maintenance and abandonment concern.
The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old registry release, this materially increases abandonment risk.
The manifest declares MIT while the artifact and repository license file are detected as BSD-2-Clause. The presence of license files is positive, but this mismatch creates legal and transparency uncertainty.
There are two open issues but no new or closed issues and no pull requests in the last month, indicating little recent maintenance activity.
Composer is used for builds, but no security-scanning tools are present. This is a hygiene gap rather than proof of unsafe code, though it reduces transparency for a package handling API credentials.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Andrew Mc Cormack |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version 6.3.* | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.