@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Standard hex decoding of blockchain block IDs, not payload obfuscation. | ai | |
| source-diff | obfuscated-file:dist/hiveauth-aes.bundle.js | AI (source-diff): Webpack bundle output for hive auth crypto helpers; not true obfuscation. | ai | |
| phantom-deps | phantom-dep:hive-tx | AI (phantom-deps): Used via config/build tooling, not a direct import; stable FP. | ai | |
| source-diff | obfuscated-file:dist/ledger-hive-tx.bundle.js | AI (source-diff): Webpack bundle output for ledger tx signing; not true obfuscation. | ai | |
| 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:@engrave/ledger-app-hive | AI (dependencies): Ledger Hive app integration is expected for a multi-provider Hive auth library. | ai | |
| dependencies | unvetted-dep:keychain-sdk | AI (dependencies): Hive Keychain SDK is a domain-appropriate dependency for a Hive authentication 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 33 of 33)
| 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 | |
| 1.5.6 | 6 / 6 | |
| 1.5.5 | 6 / 6 | |
| 1.5.4 | 6 / 7 | |
| 1.5.3 | 6 / 7 | |
| 1.5.2 | 6 / 7 | |
| 1.5.1 | 6 / 7 | |
| 1.5.0 | 6 / 7 | |
| 1.4.1 | 9 / 7 | |
| 1.4.0 | 9 / 7 | |
| 1.3.11 | 10 / 6 | |
| 1.3.10 | 10 / 6 | |
| 1.3.9 | 10 / 6 | |
| 1.3.8 | 10 / 6 | |
| 1.3.7 | 10 / 6 | |
| 1.3.6 | 10 / 6 | |
| 1.3.5 | 10 / 6 | |
| 1.3.4 | 10 / 6 | |
| 1.3.3 | 10 / 6 | |
| 1.3.2 | 10 / 6 | |
| 1.3.1 | 10 / 6 | |
| 1.3.0 | 9 / 6 | |
| 1.2.0 | 10 / 6 | |
| 1.1.0 | 10 / 6 | |
| 1.0.0 | 10 / 6 |
v1.5.6
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
v1.5.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.