@ngneat/helipopper
A Powerful Tooltip and Popover for Angular Applications
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established ngneat org package; absence of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dep in package.json; phantom-dep false positive for Angular compiled packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 13.1.2 | 3 / 0 | |
| 13.1.1 | 3 / 0 | |
| 13.1.0 | 3 / 0 | |
| 13.0.0 | 3 / 0 | |
| 12.2.0 | 3 / 0 | |
| 12.1.2 | 3 / 0 |
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.