@getodk/web-forms
ODK Web Forms
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-BHqSQfYt.js | AI (source-diff): Standard Vite minified bundle output; readable Vue/JS code with shortened variable names, not malicious obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-BHqSQfYt.js | AI (source-diff): Network calls and dynamic code in a UI framework bundle are expected; no dropper/loader pattern present. | ai | |
| source-diff | obfuscated-file:dist/MapBlock-Dkmhm_uR.js | AI (source-diff): Standard Vite minified bundle for the new map feature; sample shows normal Vue component code. | ai | |
| phantom-deps | phantom-dep:primelocale | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:@formatjs/intl | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:ol | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:vue-draggable-plus | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:image-blob-reduce | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:@mdi/js | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Bundled via Vite; phantom-dep heuristic can't trace imports through build output. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 7 / 26 | |
| 0.23.1 | 5 / 26 | |
| 0.23.0 | 5 / 26 | |
| 0.22.0 | 5 / 26 | |
| 0.21.0 | 4 / 25 | |
| 0.20.0 | 4 / 25 | |
| 0.18.2 | 4 / 25 | |
| 0.18.1 | 4 / 25 | |
| 0.18.0 | 4 / 25 | |
| 0.17.0 | 4 / 21 | |
| 0.16.0 | 4 / 21 | |
| 0.15.0 | 2 / 21 | |
| 0.14.0 | 2 / 21 | |
| 0.13.1 | 2 / 21 | |
| 0.13.0 | 2 / 21 | |
| 0.12.0 | 2 / 21 | |
| 0.11.1 | 2 / 21 | |
| 0.11.0 | 2 / 21 |
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.