Encrypted Content-Encoding for HTTP
78%
Total Score
100
89
67
The package has 22 releases over roughly 11 years, but none in the last 12 months and its latest registry release was about two years ago. Recent repository commits partly compensate for the stale registry cadence.
No build tool or security scanning tool was detected. That weakens maintenance and security transparency, although the repository's active contributors provide some compensation.
The repository has no published security policy. This is a transparency gap for a package implementing cryptographic content encoding, even though it does not establish a defect.
Both workflows use read-only permissions and the audit found no high-confidence dangerous findings, but all five action references are unpinned. Unpinned actions leave more room for unexpected upstream changes.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.