alrik11es/stupidly-simple-calendar
MIT licensing, tests, and a substantial README support adoption mechanics. The single runtime dependency and lack of install scripts limit operational complexity, but the project offers no security policy.
43%
Total Score
50
100
86
83
Health Score Breakdown
The latest release was on May 19, 2017, and there have been no releases in the last 12 months. That long release gap materially increases abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has seen no recent maintenance.
The linked repository is named calendar rather than the package name and does not mention the package in its README, creating uncertainty about whether it is the package's actual source repository.
The repository has no documented security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap, especially for a dependency intended for application use.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Marcos Sigueros Fernández |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 12 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.