@cipherstash/auth
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Standard wasm-pack build artifact for native binding, not a backdoor. | ai | |
| source-diff | encoded-string-file:wasm/stack_auth_wasm_inline.js | AI (source-diff): Base64-embedded wasm bytes from documented inline-wasm build script. | ai | |
| source-diff | obfuscated-file:wasm/stack_auth_wasm_inline.js | AI (source-diff): Base64-embedded wasm bytes from documented inline-wasm build script, not obfuscation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): wasm-bindgen generated glue code pattern. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): wasm-bindgen generated glue code pattern for WASM instantiation. | ai | |
| provenance | publisher-changed | AI (provenance): CI/CD (GitHub Actions) publisher change, consistent with automated release pipeline. | ai | |
| source-diff | net-exec-file:wasm/stack_auth_wasm_bg.js | AI (source-diff): Standard wasm-bindgen generated bindings; fetch/exec used for WASM loading, not exfil. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard NAPI-RS platform binary loader; pkg is constrained to known optional dependency names. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.42.0 | 1 / 3 | |
| 0.41.0 | 1 / 3 | |
| 0.40.0 | 0 / 3 | |
| 0.39.0 | 0 / 3 | |
| 0.38.0 | 0 / 3 | |
| 0.36.0 | 0 / 3 | |
| 0.35.0 | 0 / 3 | |
| 0.34.2 | 0 / 3 | |
| 0.34.1 | 0 / 3 | |
| 0.34.0 | 0 / 3 |
v0.42.0
3 findingsPackage contains compiled binaries that could be backdoors: • wasm/stack_auth_wasm_bg.wasm
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
4 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
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.