toasted-notifier
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
aetherinox
Keywords
push notificationsnotificationsmacosxlinuxwindowsmac os x 10.8notifytoaststoasterterminal-notifiernotify-sendgrowlwindows 7windows 8windows 10windows 11
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled binaries are the notification backends (terminal-notifier, notifu, ntfyToast) — core to this desktop notification library's function. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to invoke bundled notification binaries; expected pattern for this type of library. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): cp.exec invokes the notification binary with user-supplied options — standard pattern for node-notifier style packages. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 10.1.0 | 5 / 17 |
v10.1.0
2 findings
HIGH
Bundled binary files (4)
npm-metadata
Package contains compiled binaries that could be backdoors: • vendor/mac.noindex/terminal-notifier.app/Contents/MacOS/terminal-notifier • vendor/notifu/notifu.exe • vendor/notifu/notifu64.exe • vendor/ntfyToast/ntfytoast.exe
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.