@salutejs/plasma-new-hope
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Used transitively via react-popper; not directly imported but legitimately declared as a peer/runtime dep for this UI kit. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Used transitively via @floating-ui/react; indirect usage pattern is expected in this UI kit. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react-dom | AI (phantom-deps): Used transitively via @floating-ui/react; indirect usage pattern is expected in this UI kit. | ai | |
| phantom-deps | phantom-dep:@salutejs/input-core | AI (phantom-deps): Same org scope; likely used indirectly via @salutejs/react-maskinput. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.363.1 | 22 / 36 | |
| 0.363.0 | 22 / 36 | |
| 0.361.0 | 22 / 36 | |
| 0.360.0 | 22 / 36 | |
| 0.359.0 | 22 / 36 | |
| 0.358.0 | 22 / 36 | |
| 0.357.0 | 22 / 36 |
v0.363.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.363.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.361.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.359.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.358.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.357.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.