@enhavo/vue-form
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used in a form expression evaluator to run user-defined expressions; not a supply-chain payload pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package in a known monorepo; sparse README is a style choice, not a spam indicator. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in form expression evaluator with controlled args; consistent with template engine pattern in this package. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): qs is declared as a runtime dep and likely used indirectly via axios or config; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.15.13 | 3 / 0 | |
| 0.15.12 | 3 / 0 | |
| 0.15.11 | 3 / 0 | |
| 0.15.10 | 3 / 0 | |
| 0.15.9 | 3 / 0 | |
| 0.15.8 | 3 / 0 | |
| 0.15.7 | 3 / 0 | |
| 0.15.6 | 3 / 0 | |
| 0.15.5 | 3 / 0 | |
| 0.15.4 | 3 / 0 | |
| 0.15.3 | 3 / 0 | |
| 0.15.2 | 3 / 0 | |
| 0.15.1 | 3 / 0 | |
| 0.14.7 | 2 / 0 | |
| 0.14.6 | 2 / 0 | |
| 0.14.5 | 2 / 0 |
v0.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.