lutsen/updrive
The README explains setup, and the package includes a license with a small dependency surface. It lacks tests, security scanning, and a security policy, leaving little evidence for safe ongoing maintenance.
38%
Total Score
100
64
75
Health Score Breakdown
Only one release exists, published in November 2016, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended for ongoing use.
Composer is used for builds, but no security scanning tooling is present. That is a maintenance and transparency gap for a package that handles Google Drive uploads.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was also in November 2016 and does not offset the inactive release history.
No repository security policy was found, leaving no documented process for reporting or handling vulnerabilities.
The latest version is v0.5 and is not marked as a stable major release, adding maturity concerns alongside the very old release history.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Lútsen Stellingwerff |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 google/apiclient Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.