@encatch/web-sdk
A lightweight, type-safe JavaScript SDK for integrating Encatch forms and surveys
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with good track record; no-provenance is a low signal for this package. | ai | |
| source-diff | obfuscated-file:dist-sdk/plugin/sdk/core-wrapper-CQ0WhLhZ.js | AI (source-diff): Vite-minified bundle with hashed filename; sample shows readable Preact hooks code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist-sdk/plugin/sdk/core-wrapper-2TN8GbgP.js | AI (source-diff): Long lines are Vite minified output; code structure is readable Preact hooks — not obfuscation. | ai | |
| source-diff | obfuscated-file:dist-sdk/plugin/sdk/core-wrapper-Ag91pd4Q.js | AI (source-diff): Vite/Rollup minified bundle; sample shows readable Preact hooks code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist-sdk/plugin/sdk/core-wrapper-sV_pMBBg.js | AI (source-diff): Vite/Rollup build artifact; minified bundle with readable Preact hooks code, not malicious obfuscation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in Proxy trap handler within bundled framework code — standard pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:preact-iso | AI (phantom-deps): Declared in dependencies and bundled by Vite; not directly imported in source but legitimately used. | ai | |
| phantom-deps | phantom-dep:lucide-preact | AI (phantom-deps): Declared in dependencies and bundled by Vite; not directly imported in source but legitimately used. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 0 / 4 | |
| 1.2.0 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 0.0.34 | 7 / 6 | |
| 0.0.33 | 7 / 6 | |
| 0.0.32 | 7 / 6 | |
| 0.0.31 | 7 / 6 | |
| 0.0.30 | 7 / 6 | |
| 0.0.29 | 7 / 6 | |
| 0.0.23 | 9 / 4 | |
| 0.0.21 | 9 / 4 | |
| 0.0.20 | 9 / 4 | |
| 0.0.19 | 9 / 4 | |
| 0.0.18 | 9 / 4 | |
| 0.0.17 | 9 / 4 | |
| 0.0.16 | 9 / 4 | |
| 0.0.15 | 9 / 4 | |
| 0.0.14 | 9 / 4 | |
| 0.0.13 | 9 / 4 |
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: godwin.pinto.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.