JSON canonicalize function
86%
Total Score
80
100
95
75
100
One registry publisher is consistent with a small open-source project, but registry access records do not demonstrate broader operational redundancy.
The repository is owned by an individual rather than an organization, so the small publisher and contributor base provide less institutional handoff capacity.
The repository reports no build tool or security scanning tool. For this small package the build gap is limited, but the absence of security scanning is a modest transparency weakness.
No repository security policy was found, leaving vulnerability-reporting expectations unclear despite otherwise active maintenance.
Both workflows were analyzed without untrusted triggers or script-injection sinks. Two of four action references are unpinned and a high-severity cache-poisoning finding has low confidence, while high-confidence adhoc package installation is a minor hygiene 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.