Simple config handling for your app or module
82%
Total Score
60
95
75
50
No build attestation or trusted-publisher identity is present, leaving the relationship between source and published artifact less independently verifiable.
A prepare script runs during installation or packaging, adding a small execution-surface concern even though the signal does not show harmful behavior.
One registry account has publish access, which concentrates publishing authority; repository activity shows the same individual is currently maintaining the project.
The repository is owned by an individual rather than an organization, so the concentrated contributor and publisher base has no visible organizational handoff support.
All one recent commit came from a single contributor, concentrating current maintenance responsibility and increasing continuity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ajv Version ^8.17.1 | — | — |
semver Version ^7.7.2 | — | — |
dot-prop Version ^10.0.0 | — | — |
env-paths Version ^3.0.0 | — | — |
atomically Version ^2.0.3 | — | — |
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.