@aioha/aioha
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/tx-digest.bundle.js | AI (source-diff): Webpack bundle of same-org @aioha/tx-digest; generated by documented prepublish script, not injected obfuscation. | ai | |
| dependencies | unvetted-dep:keychain-sdk | AI (dependencies): Hive Keychain SDK is a domain-appropriate dependency for a Hive authentication library. | ai | |
| dependencies | unvetted-dep:@engrave/ledger-app-hive | AI (dependencies): Ledger Hive app integration is expected for a multi-provider Hive auth library. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-transport-webusb | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@hiveio/dhive | AI (dependencies): @hiveio/dhive is the canonical Hive blockchain library; its use is expected and stable for this Hive auth package. | ai | |
| phantom-deps | phantom-dep:@aioha/tx-digest | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly via build output rather than direct import. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.8.5 | 6 / 7 | |
| 1.8.4 | 6 / 7 | |
| 1.8.3 | 6 / 7 | |
| 1.8.2 | 7 / 6 | |
| 1.8.1 | 7 / 6 | |
| 1.8.0 | 7 / 6 | |
| 1.7.0 | 5 / 6 | |
| 1.6.1 | 4 / 7 | |
| 1.6.0 | 6 / 6 |
v1.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
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.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.