@xyo-network/hash
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/node/worker/wasmHash-bundle.mjs | AI (source-diff): Base64-encoded WASM binaries from hash-wasm dependency, not injected payloads. | ai | |
| source-diff | obfuscated-file:dist/node/worker/wasmHash-bundle.mjs | AI (source-diff): esbuild bundle of hash-wasm; long lines are WASM binary payloads, not obfuscation. | ai | |
| provenance | missing-githead | AI (provenance): Minor CI environment change; no material code diff from prior version. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual (joelbcarter) to org account (xyo) with 1006 approved packages; consistent with org consolidation. | ai | |
| source-diff | encoded-string-file:dist/browser/worker/wasmHash-bundle.mjs | AI (source-diff): Base64-encoded WASM binary for SHA-256; expected artifact from the wasmHashBundle build script. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @xyo-network/wasm is a same-org dependency matching the package's hashing purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large, established monorepo; sparse README/keywords are typical for scoped sub-packages. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @xyo-network/hash is not a typosquat of hapi; Levenshtein match is spurious. | ai |
Versions (showing 51 of 110)
| Version | Deps | Published |
|---|---|---|
| 7.0.15 | 1 / 23 | |
| 7.0.14 | 1 / 18 | |
| 7.0.13 | 1 / 20 | |
| 7.0.12 | 1 / 6 | |
| 7.0.11 | 1 / 6 | |
| 7.0.10 | 1 / 6 | |
| 7.0.9 | 1 / 6 | |
| 7.0.8 | 1 / 6 | |
| 7.0.7 | 1 / 6 | |
| 7.0.6 | 1 / 6 | |
| 7.0.5 | 1 / 22 | |
| 7.0.4 | 1 / 22 | |
| 7.0.3 | 1 / 20 | |
| 7.0.2 | 1 / 20 | |
| 7.0.0 | 1 / 20 | |
| 6.1.1 | 1 / 20 | |
| 6.1.0 | 1 / 20 | |
| 6.0.9 | 1 / 23 | |
| 6.0.8 | 1 / 24 | |
| 6.0.7 | 1 / 25 | |
| 6.0.6 | 1 / 25 | |
| 6.0.5 | 1 / 26 | |
| 6.0.4 | 1 / 27 | |
| 6.0.3 | 1 / 27 | |
| 6.0.2 | 1 / 27 | |
| 6.0.1 | 1 / 27 | |
| 6.0.0 | 1 / 27 | |
| 5.6.3 | 1 / 27 | |
| 5.6.2 | 1 / 27 | |
| 5.5.2 | 1 / 28 | |
| 5.5.1 | 1 / 28 | |
| 5.5.0 | 0 / 48 | |
| 5.4.1 | 2 / 17 | |
| 5.4.0 | 2 / 17 | |
| 5.3.30 | 2 / 19 | |
| 5.3.29 | 2 / 19 | |
| 5.3.27 | 3 / 19 | |
| 5.3.26 | 3 / 20 | |
| 5.3.25 | 3 / 20 | |
| 5.3.24 | 3 / 20 | |
| 5.3.22 | 3 / 20 | |
| 5.3.20 | 3 / 12 | |
| 5.3.17 | 3 / 11 | |
| 5.3.16 | 3 / 11 | |
| 5.3.15 | 3 / 9 | |
| 5.3.13 | 3 / 9 | |
| 5.3.12 | 3 / 9 | |
| 5.3.11 | 3 / 9 | |
| 5.3.10 | 3 / 9 | |
| 5.3.8 | 3 / 9 | |
| 5.3.7 | 3 / 9 |
v7.0.15
2 findingsModified file contains 22 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.
v7.0.14
2 findingsModified file contains 22 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.
v7.0.13
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.
v7.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.