@biowasm/aioli
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/aioli.js | AI (source-diff): Base64-embedded bundled worker code (comlink), unchanged from prior approved version. | ai | |
| source-diff | encoded-string-file:dist/aioli.mjs | AI (source-diff): Same bundled worker payload, unchanged from prior approved version. | ai | |
| phantom-deps | phantom-dep:comlink | AI (phantom-deps): Used inside bundled worker code, not directly imported at source level. | ai | |
| phantom-deps | phantom-dep:wasm-feature-detect | AI (phantom-deps): Used inside bundled build, not directly imported at source level. | ai |
v3.2.2
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.