@akinon/ui-notification
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Akinon internal UI component package; sparse metadata is consistent across their published packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; publisher has strong approval track record with no malware signals. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org UI package; missing metadata is a style issue, not a spam/malware indicator for this publisher namespace. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.4.9 | 2 / 5 | |
| 1.4.7 | 2 / 5 | |
| 1.4.4 | 2 / 5 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 1.2.0 | 2 / 5 |
v1.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.