@pnotify/core
PNotify Core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@smui/common | AI (phantom-deps): Used in Svelte component markup, not scannable as a JS import. | ai | |
| phantom-deps | phantom-dep:svelte | AI (phantom-deps): Svelte is referenced via config/svelte field, not a direct JS import. | ai | |
| dependencies | unvetted-dep:@smui/common | AI (dependencies): Well-known Svelte Material UI component library, benign dependency. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @pnotify/core is the legitimate PNotify notification library, not a typosquat of cors. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 0 / 10 | |
| 5.1.2 | 0 / 10 | |
| 5.1.1 | 0 / 12 | |
| 5.1.0 | 2 / 9 | |
| 5.0.1 | 2 / 9 | |
| 5.0.0 | 0 / 11 |
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.