Validate JSON
68%
Total Score
67
100
88
83
100
One contributor made all two recent commits, concentrating current maintenance responsibility. Organization ownership provides some ability to hand work off, but no second active contributor is shown.
The repository had two commits in the last three months, so it is not inactive, but the observed activity is limited.
The repository name does not match the package name and its README does not mention this package, so the package-to-repository relationship is not clearly established. The package README does describe it as a Mapbox GL JS fork, which partially explains the mismatch but does not remove the transparency gap.
The repository uses Make for builds, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of abandonment.
Both workflows use all four analyzed actions without pinning, and one release workflow grants top-level write permissions. The two cache-poisoning findings are low-confidence hygiene alerts, so they do not independently indicate a severe workflow risk.
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.