ml/itsdangerous
Its small release history and lack of recent repository commits limit confidence in ongoing maintenance. Tests, a clear license, and a recent release provide useful support, but the workflow uses three unpinned actions.
60%
Total Score
75
100
92
67
Health Score Breakdown
The package has only 2 releases across about 9 years, with a median interval of about 8.8 years. One release in the last 12 months and the recent latest release partly offset the unusually sparse history.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, which weakens evidence of continuing maintenance. The release on February 10, 2026 shows some recent activity but does not establish an ongoing cadence.
The repository has no security policy, leaving vulnerability-reporting and response expectations unclear. This is a transparency gap, not evidence that the package is unsafe.
All 3 analyzed action uses are unpinned, creating avoidable build reproducibility and update risk. The audit found no dangerous triggers, untrusted checkouts, script injection, or other reported findings, which limits the concern to hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 months 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.