Properties file reader for Node.js
78%
Total Score
50
100
94
80
100
There were no commits and no active maintainers in the last three months, a concrete sign that maintenance may currently be paused despite the recent release history.
There is one open issue and five open pull requests, but none were created or merged in the last month, suggesting limited recent project activity.
The repository uses TypeScript, tsup, npm scripts, and SWC for its build, but no security-scanning tools were detected. The build setup is healthy, while the missing scanning is a modest transparency gap.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a hygiene gap rather than evidence that the package is unsafe.
One workflow has explicit top-level write permissions and another has no top-level permissions declaration, so workflow access controls are not uniformly minimal; one workflow does declare read-only permissions.
| Title | Versions | Severity |
|---|---|---|
CVE-2020-28471 properties-reader is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 0.0.0 - 2.2.0. | 0.0.0 - 2.2.0 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
mkdirp Version ^3.0.1 | — | — |
@kwsites/file-exists Version ^1.1.1 | — | — |
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.