@novu/nextjs
Novu <Inbox /> Next.js SDK
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @novu/nextjs is an intentional Next.js integration package, not a typosquat of 'next'. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.18.1 | 1 / 7 | |
| 3.18.0 | 1 / 7 | |
| 3.17.0 | 1 / 7 | |
| 3.16.0 | 1 / 7 | |
| 3.15.0 | 1 / 7 | |
| 3.3.1 | 1 / 7 | |
| 3.3.0 | 1 / 7 | |
| 3.2.0 | 1 / 7 | |
| 3.1.0 | 1 / 7 | |
| 3.0.3 | 1 / 7 | |
| 3.0.2 | 1 / 7 | |
| 3.0.0 | 1 / 7 |
v3.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.