mspconcepts/ddscalendar
The project has seen no release activity for about nine years, and its repository has not been updated since July 2017. It also lacks a license and security policy, leaving maintenance and usage rights unclear.
35%
Total Score
71
50
Health Score Breakdown
The package has only three releases, all clustered in July 2017, with no releases in the last 12 months; this is strong evidence of abandonment for a library dependency.
Neither the package metadata nor the artifact or repository contains a license, so usage rights are unclear and the package is harder to adopt safely.
The package declares post-create, post-install, and post-update scripts. These add installation-time behavior that deserves scrutiny, although the signal alone does not establish a severe risk.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was in July 2017 and does not offset the long period without releases.
The linked repository has no security policy. This is a transparency gap for a package integrating with Google Calendar, though it is less significant than the lack of maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Manoj Sonagra |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spatie/laravel-google-calendar Version ^1.1 | — | — |
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.