@huggingface/jinja 0.5.10 appears to be a healthy dependency: it has a sustained release history over nearly 3 years, recent releases, active development in an organization-owned repository, broad contributor participation, build provenance, and a small runtime dependency surface. The artifact is licensed, typed, and includes source files, while repository tests compensate for the absence of packaged tests. The main reservations are the lack of a security policy and incomplete or broadly write-enabled workflow permission declarations, but the workflows show no analyzed pull-request-target, untrusted-checkout, or script-injection patterns, and repository security scanning is enabled. The package is not deprecated or archived and is reasonable to adopt, subject to normal review of future releases.
92%
Total Score
100
100
95
80
100
No repository security policy was found, which weakens vulnerability-reporting transparency and is a genuine hygiene gap, although other security controls are present.
Six workflows lack top-level permissions and 17 declare top-level write permissions, indicating weaker least-privilege workflow hygiene; this is partly mitigated by the absence of dangerous workflow patterns and the repository's security scanning.
Version 0.5.10 is not a stable-major release, but it is not prerelease and recent prerelease share is 0%, so the versioning status is a modest maturity limitation rather than a major concern.
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.