InfoCode
How to fix: Push Notification API Usage
Push API/notifications usage detected.
Why it matters
Privacy concern if abused.
Push notifications require user consent.
How to fix it
- 1Ensure notifications are used appropriately.
Code examples
Require explicit user permission for Push API
async function subscribePush() {
const permission = await Notification.requestPermission();
if (permission !== "granted") return null;
const reg = await navigator.serviceWorker.ready;
return reg.pushManager.subscribe({
userVisibleOnly: true, // must be true, prevents silent push
applicationServerKey: urlBase64ToUint8Array(VAPID_PUBLIC_KEY),
});
}References
Detected automatically by VulnRadar. The check id is push-api-usage, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Push Notification API Usage?
- VulnRadar rates this info severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id push-api-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.