@tootallnate/once
3.0.1 · 9 Feb 2026MIT60.7M / weekRepositoryHomepagenpmAtom feed
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 ScopingGHSA-vpq2-c234-7xj6 · 3 Mar 2026fixed in 3.0.1, 2.0.1
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
- Licence
- ProvenancePresent, built from github.com/TooTallNate/onceSays where the release was built and from which commit. It does not say the code is safe.
- Published byGitHub 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
- Size
- GitHub stars27 on tootallnate/once
- Last release3.0.1, 9 February 2026
- OpenSSF Scorecard2.8 / 10 · 24 Aug 2026Lowest: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0, Fuzzing 0Grades 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: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.