@eva/plugin-renderer-mesh MIT 2 versions

@eva/plugin-renderer-mesh

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
provenance	no-provenance	AI (provenance): Consistent across all eva.js org packages; not a per-version risk.	ai	2026/05/18
phantom-deps	phantom-dep:@eva/inspector-decorator	AI (phantom-deps): Same-org scoped dep declared but used indirectly; stable false positive for this monorepo package.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Sparse README/description is typical of @eva monorepo sub-packages across all 57 versions.	ai	2026/04/29

Versions (showing 2 of 2)

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

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.