@permaweb/libs
Documentation for this SDK can be found at the [top level](https://github.com/permaweb/permaweb-libs) of the repository.
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 | source-size-tripled | AI (source-diff): Bundled dependency (arbundles + crypto libs) inflates dist size, not injected payload. | ai | |
| dependencies | unvetted-dep:@dha-team/arbundles | AI (dependencies): Arweave-ecosystem dep matching publisher's own org. | ai | |
| npm-metadata | url-dep:@arx/sdk | AI (npm-metadata): file: path is a local sibling package in this org's monorepo. | ai | |
| dependencies | unvetted-dep:@arx/sdk | AI (dependencies): Local monorepo path within same org, not external unvetted code. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): esbuild-bundled dist output, not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/bundle.esm.js | AI (source-diff): Bundled arweave SDK network calls, no dropper behavior. | ai | |
| phantom-deps | phantom-dep:crypto-browserify | AI (phantom-deps): Browser polyfill referenced in esbuild config; stable for this package. | ai | |
| phantom-deps | phantom-dep:@ardrive/turbo-sdk | AI (phantom-deps): Build-time/config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-alias | AI (phantom-deps): Build-time plugin referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:web-streams-polyfill | AI (phantom-deps): Browser polyfill referenced in esbuild config; stable for this package. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-polyfill-node | AI (phantom-deps): Build-time plugin referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:stream-browserify | AI (phantom-deps): Browser polyfill referenced in esbuild config; stable for this package. | ai | |
| phantom-deps | phantom-dep:arweave | AI (phantom-deps): Build-time polyfill/config reference pattern; stable for this dual-build package. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): Build-time polyfill/config reference pattern; stable for this dual-build package. | ai | |
| phantom-deps | phantom-dep:tsc-alias | AI (phantom-deps): Build-time tool referenced in config; stable for this package. | ai | |
| phantom-deps | phantom-dep:@permaweb/arx | AI (phantom-deps): Same-org dep referenced in build config; stable false positive. | ai | |
| phantom-deps | phantom-dep:os-browserify | AI (phantom-deps): Browser polyfill referenced in esbuild config; stable for this package. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Long strings are esbuild minified output (polyfills/bundled deps), not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:dist/index.esm.js | AI (source-diff): Long strings are esbuild minified output (polyfills/bundled deps), not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long strings are esbuild minified output (polyfills/bundled deps), not obfuscated payloads. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README/no keywords is cosmetic; package is a legitimate permaweb SDK with 81 versions and a real GitHub repo. | ai | |
| phantom-deps | phantom-dep:@dha-team/arbundles | AI (phantom-deps): Declared dep used indirectly via bundled output; phantom-dep false positive for this package. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.0.94 | 2 / 23 | |
| 0.0.93 | 2 / 23 | |
| 0.0.92 | 2 / 23 | |
| 0.0.91 | 2 / 23 | |
| 0.0.90 | 2 / 23 | |
| 0.0.89 | 2 / 23 | |
| 0.0.88 | 2 / 23 | |
| 0.0.87 | 2 / 23 | |
| 0.0.86 | 1 / 23 | |
| 0.0.85 | 1 / 23 | |
| 0.0.84 | 1 / 23 | |
| 0.0.83 | 1 / 23 | |
| 0.0.82 | 1 / 23 | |
| 0.0.81 | 1 / 23 | |
| 0.0.80 | 1 / 23 | |
| 0.0.79 | 1 / 23 | |
| 0.0.78 | 1 / 23 | |
| 0.0.77 | 1 / 23 | |
| 0.0.76 | 1 / 23 | |
| 0.0.75 | 1 / 23 | |
| 0.0.74 | 1 / 23 | |
| 0.0.73 | 1 / 23 | |
| 0.0.72 | 1 / 23 | |
| 0.0.71 | 1 / 23 | |
| 0.0.70 | 1 / 23 | |
| 0.0.69 | 1 / 23 | |
| 0.0.68 | 1 / 23 | |
| 0.0.67 | 1 / 23 | |
| 0.0.66 | 1 / 23 | |
| 0.0.64 | 1 / 23 | |
| 0.0.63 | 1 / 21 | |
| 0.0.55 | 1 / 21 | |
| 0.0.54 | 1 / 21 | |
| 0.0.53 | 1 / 21 | |
| 0.0.52 | 1 / 21 | |
| 0.0.51 | 1 / 21 | |
| 0.0.38 | 0 / 17 | |
| 0.0.37 | 0 / 17 | |
| 0.0.36 | 12 / 13 | |
| 0.0.35 | 12 / 13 | |
| 0.0.34 | 12 / 13 | |
| 0.0.33 | 13 / 13 | |
| 0.0.32 | 11 / 13 | |
| 0.0.29 | 11 / 13 | |
| 0.0.26 | 4 / 13 | |
| 0.0.25 | 4 / 13 | |
| 0.0.24 | 4 / 13 | |
| 0.0.23 | 4 / 13 | |
| 0.0.22 | 4 / 13 | |
| 0.0.21 | 4 / 13 | |
| 0.0.20 | 4 / 13 | |
| 0.0.19 | 4 / 13 | |
| 0.0.18 | 4 / 13 | |
| 0.0.17 | 4 / 13 | |
| 0.0.16 | 2 / 8 | |
| 0.0.15 | 2 / 8 | |
| 0.0.14 | 2 / 8 | |
| 0.0.13 | 2 / 8 | |
| 0.0.12 | 2 / 8 | |
| 0.0.11 | 2 / 8 | |
| 0.0.1 | 2 / 7 |
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
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.
v0.0.33
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.
v0.0.32
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.
v0.0.29
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.
v0.0.26
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.
v0.0.25
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.