---
title: "@pkgr/core security advisories"
description: "2 known security advisories for @pkgr/core, with the versions they affect and the version that fixes each."
url: https://inlinr.com/packages/@pkgr/core/security
lang: en
---

[Packages](https://inlinr.com/packages)

# @pkgr/core

0.3.6 · 28 May 2026 MIT 55.6M / week [Repository](https://github.com/un-ts/pkgr) [Homepage](https://github.com/un-ts/pkgr/blob/master/packages/core) [npm](https://www.npmjs.com/package/@pkgr/core) [Atom feed](https://inlinr.com/packages/feed/@pkgr/core)

Your version 

## Security advisories

From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.

| Line | Newest | Where it stands   |
| ---- | ------ | ----------------- |
|      | 0.3.6  | No known advisory |
|      | 0.2.10 | Safe from 0.2.9   |

- High  
[eslint-config-prettier, eslint-plugin-prettier, synckit, @pkgr/core, napi-postinstall have embedded malicious code](https://inlinr.com/advisories/GHSA-f29h-pxvx-f335)GHSA-f29h-pxvx-f335 · 19 Jul 2025  
fixed in 0.2.9
- Malicious  
[Malicious code in @pkgr/core (npm)](https://inlinr.com/advisories/MAL-2025-6021)MAL-2025-6021 · 21 Jul 2025  
safe in 0.3.6

### Quality and security signals

What [npm](https://www.npmjs.com/package/@pkgr/core) and [deps.dev](https://deps.dev/npm/%40pkgr%2Fcore) say about the latest release. Signals, not a verdict.

Reading npm and deps.dev…

Reading releases, release notes and advisories…

Registry facts last checked 3 Nov 2026\. Releases and advisories last read 3 Nov 2026.