@eva/plugin-renderer-lottie MIT 3 versions

@eva/plugin-renderer-lottie

npm Homepage

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

aspsndaz8641683bezoswiseyurijimizaiterrykingcha

Keywords

eva.js

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Part of the eva.js plugin ecosystem; sparse README/description is a documentation style choice, not a spam indicator.	ai	2026/05/18
provenance	no-provenance	AI (provenance): Established package with 210 versions; lack of provenance is consistent across all prior releases.	ai	2026/05/18

Versions (showing 3 of 3)

Version	Deps	Published
2.0.2	4 / 0	2026-05-27
2.0.1	4 / 0	2026-04-21
2.0.0	4 / 0	2025-08-22

v2.0.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.