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

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

# @tootallnate/once

3.0.1 · 9 Feb 2026 MIT 60.7M / week [Repository](https://github.com/TooTallNate/once) [Homepage](https://github.com/TooTallNate/once#readme) [npm](https://www.npmjs.com/package/@tootallnate/once) [Atom feed](https://inlinr.com/packages/feed/@tootallnate/once)

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                                                        |
| ---- | ------ | ---------------------------------------------------------------------- |
|      | 3.0.1  | Safe from 3.0.1                                                        |
|      | 2.0.1  | Safe from 2.0.1                                                        |
|      | 1.1.2  | 1 open advisory, worst low  · last release Apr 2020, no longer updated |

- Low  
[@tootallnate/once vulnerable to Incorrect Control Flow Scoping](https://inlinr.com/advisories/GHSA-vpq2-c234-7xj6)GHSA-vpq2-c234-7xj6 · 3 Mar 2026  
fixed in 3.0.1, 2.0.1

### Quality and security signals

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

- Licence  
[MIT](https://spdx.org/licenses/MIT.html)
- Provenance  
[Present](https://www.npmjs.com/package/@tootallnate/once/v/3.0.1#provenance), built from [github.com/TooTallNate/once](https://github.com/TooTallNate/once)  
Says where the release was built and from which commit. It does not say the code is safe.
- Published by  
GitHub Actions3.0.1 was published by a different account than 3.0.0 (tootallnate). Often a new team member, sometimes a taken-over account.
- Maintainers on npm  
[tootallnate](https://www.npmjs.com/~tootallnate)
- Size  
[26 kB unpacked , 15 files](https://www.npmjs.com/package/@tootallnate/once/v/3.0.1?activeTab=code)
- GitHub stars  
27 on [tootallnate/once](https://github.com/tootallnate/once)
- Last release  
[3.0.1](https://www.npmjs.com/package/@tootallnate/once/v/3.0.1), 9 February 2026
- OpenSSF Scorecard  
[2.8 / 10](https://scorecard.dev/viewer/?uri=github.com%2Ftootallnate%2Fonce) · 24 Aug 2026  
Lowest: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0, Fuzzing 0  
Grades the repository's practices (reviews, CI, branch protection), not the package's code.

Reading releases, release notes and advisories…

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

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
