vfile utility to count messages per category: failures, warnings, etc
68%
Total Score
88
100
90
80
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. This is a transparency gap, but it is not evidence that the release is unsafe by itself.
One of two workflows uses pull_request_target, which can increase workflow risk when handling untrusted pull requests. No untrusted checkout or script-injection patterns were detected, partly limiting the concern.
The package has existed since 2016 with nine releases, but it has had no release in about 3 years and no releases in the last 12 months, indicating reduced maintenance activity.
There were no commits and no active maintainers in the last 3 months, consistent with the roughly 3-year release gap and increasing abandonment risk.
The repository uses TypeScript and npm build tooling, supporting reproducible project structure, but it has no detected security-scanning tools, which reduces security-process transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
vfile Version ^6.0.0 | — | — |
vfile-message Version ^4.0.0 | — | — |
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.