@enhavo/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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 102 versions; dormancy is an artifact of comparing to an older approved version, not actual inactivity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are tiptap v2 ecosystem packages replacing tinymce — a well-known WYSIWYG editor swap, not suspicious supply-chain additions. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment is a transitive/build-config dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vuedraggable | AI (phantom-deps): vuedraggable referenced in build config; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @enhavo/form is not a typosquat of cors; Levenshtein match is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate scoped package in a large monorepo; sparse README/metadata is typical for internal ecosystem packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.15.13 | 27 / 0 | |
| 0.15.12 | 27 / 0 | |
| 0.15.11 | 27 / 0 | |
| 0.15.10 | 28 / 0 | |
| 0.15.9 | 28 / 0 | |
| 0.15.8 | 28 / 0 | |
| 0.15.7 | 28 / 0 | |
| 0.15.6 | 28 / 0 | |
| 0.15.5 | 26 / 0 | |
| 0.15.4 | 26 / 0 | |
| 0.15.3 | 25 / 0 | |
| 0.15.2 | 25 / 0 | |
| 0.15.1 | 25 / 0 | |
| 0.14.7 | 11 / 0 | |
| 0.14.6 | 11 / 0 | |
| 0.14.5 | 11 / 0 |
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.