| Version | Supported |
|---|---|
| 0.1.x | ✅ |
If you discover a security vulnerability in the Streamline WASM Transform Marketplace, please report it responsibly.
- Do NOT open a public GitHub issue for security vulnerabilities.
- Email security@streamlinelabs.dev with:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment within 48 hours of your report
- Assessment within 5 business days
- Fix timeline communicated once the issue is confirmed
- Credit in the release notes (unless you prefer anonymity)
All transforms run inside a wasmtime WebAssembly sandbox with:
- No filesystem access (unless explicitly granted via WASI capabilities)
- No network access
- Memory isolation between transforms
- CPU time limits to prevent infinite loops
- All transform entries include a
checksumfield (SHA-256 hash of the WASM binary) - The CLI verifies checksums after download before installation
- The registry is version-controlled and changes require pull request review
- Official transforms in this repository are maintained by StreamlineLabs
- Community transforms should be reviewed before installation
- Always verify the
authorandrepository_urlfields before installing third-party transforms
- Never embed secrets or credentials in WASM modules
- Validate all input data before processing
- Handle malformed JSON gracefully (return pass-through, not panic)
- Use the
pii-redactortransform for data that may contain sensitive information - Keep dependencies minimal to reduce attack surface