blamer is a tool for getting information about author of code from version control system
68%
Total Score
75
100
90
88
50
No build attestation or trusted-publisher configuration was detected, so consumers have limited evidence connecting the published artifact to its source build.
The repository recorded zero commits and zero active maintainers in the last 3 months. A release was published during the broader period, but the lack of recent source activity weakens evidence of active maintenance.
The repository has 8 stars, 9 forks, and 1 watcher, indicating a small user and contributor footprint. This is supporting caution rather than evidence that the package is unfit.
The project uses TypeScript and npm build tooling, but no security-scanning tools were detected. That is a transparency and hygiene gap, not a severe risk on its own.
No security policy was found in the repository, leaving vulnerability-reporting expectations unclear for consumers.
| Title | Versions | Severity |
|---|---|---|
CVE-2023-26143 blamer is vulnerable to Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in versions 0.0.0 - 1.0.4. | 0.0.0 - 1.0.4 | Medium |
CVE-2019-10807 blamer is vulnerable to Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in versions 0.0.0 - 1.0.1. | 0.0.0 - 1.0.1 | Critical |
CVE-2020-8137 blamer is vulnerable to Improper Control of Generation of Code ('Code Injection') in versions 0.0.0 - 1.0.0. | 0.0.0 - 1.0.0 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
execa Version ^4.0.0 | — | — |
which Version ^2.0.2 | — | — |
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.