@arbidocs/sdk
Shared operations layer for ARBI — auth, config, SSE, WebSocket, and API operations
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser-BbUObdvG.d.cts | AI (source-diff): TypeScript declaration file with long doc comments, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-BbUObdvG.d.ts | AI (source-diff): TypeScript declaration file with long doc comments, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-Bq64bPkc.d.cts | AI (source-diff): TypeScript declaration file with long doc comments, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/browser-Bq64bPkc.d.ts | AI (source-diff): TypeScript declaration file with long doc comments, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/browser-T0w0nU41.d.cts | AI (source-diff): TS declaration file flagged by line-length heuristic; plain readable type defs, not code. | ai | |
| source-diff | obfuscated-file:dist/browser-T0w0nU41.d.ts | AI (source-diff): TS declaration file flagged by line-length heuristic; plain readable type defs, not code. | ai | |
| source-diff | obfuscated-file:dist/browser-BUspHdyk.d.ts | AI (source-diff): Type declaration file (.d.ts) with readable JSDoc; long-line heuristic false positive. | ai | |
| source-diff | obfuscated-file:dist/browser-BUspHdyk.d.cts | AI (source-diff): Type declaration file (.d.cts) with readable JSDoc; long-line heuristic false positive. | ai | |
| source-diff | obfuscated-file:dist/browser-DepiVl-4.d.ts | AI (source-diff): Type declaration file, not executable obfuscated code; long lines are generated .d.ts output. | ai | |
| source-diff | obfuscated-file:dist/browser-DepiVl-4.d.cts | AI (source-diff): Type declaration file, not executable obfuscated code; long lines are generated .d.ts output. | ai | |
| source-diff | obfuscated-file:dist/browser-CxTSIAhf.d.ts | AI (source-diff): Generated TypeScript declaration file, long lines not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/browser-CxTSIAhf.d.cts | AI (source-diff): Generated TypeScript declaration file, long lines not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/browser-BS_k043E.d.cts | AI (source-diff): Declaration file with long lines from many type exports, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-BS_k043E.d.ts | AI (source-diff): Declaration file with long lines from many type exports, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-B5b3SDW6.d.ts | AI (source-diff): TypeScript declaration file with long type unions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-B5b3SDW6.d.cts | AI (source-diff): TypeScript declaration file with long type unions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-DgApY8QV.d.cts | AI (source-diff): Generated TypeScript declaration file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-DgApY8QV.d.ts | AI (source-diff): Generated TypeScript declaration file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-C4gqnXaX.d.ts | AI (source-diff): Type declaration file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-C4gqnXaX.d.cts | AI (source-diff): Type declaration file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/browser-DYnkgkmL.d.cts | AI (source-diff): Long lines are TypeScript declaration types, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/browser-DYnkgkmL.d.ts | AI (source-diff): Long lines are TypeScript declaration types, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/browser-NpucdgQ1.d.ts | AI (source-diff): Large .d.ts type-declaration file, not executable obfuscated code. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Established high-frequency publisher with 120 versions; benign release cadence. | ai | |
| source-diff | obfuscated-file:dist/browser-NpucdgQ1.d.cts | AI (source-diff): Large .d.cts type-declaration file, not executable obfuscated code. | ai | |
| source-diff | encoded-string-file:dist/browser.cjs | AI (source-diff): Base64-encoded libsodium WASM binary data; crypto primitive names visible in decoded content confirm legitimacy. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundling libsodium WASM binary; consistent with crypto SDK adding native crypto support. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same libsodium WASM bundle pattern. | ai | |
| source-diff | encoded-string-file:dist/browser.js | AI (source-diff): Same libsodium WASM bundle pattern. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Same libsodium WASM bundle pattern as browser.cjs. | ai | |
| provenance | no-provenance | AI (provenance): Small SDK package; provenance absence is a process gap, not a security signal for this package. | ai |
Versions (showing 51 of 127)
| Version | Deps | Published |
|---|---|---|
| 0.3.126 | 2 / 5 | |
| 0.3.125 | 2 / 5 | |
| 0.3.124 | 2 / 5 | |
| 0.3.123 | 2 / 5 | |
| 0.3.122 | 2 / 5 | |
| 0.3.121 | 2 / 5 | |
| 0.3.120 | 2 / 5 | |
| 0.3.119 | 2 / 5 | |
| 0.3.118 | 2 / 5 | |
| 0.3.117 | 2 / 5 | |
| 0.3.116 | 2 / 5 | |
| 0.3.115 | 2 / 5 | |
| 0.3.114 | 2 / 5 | |
| 0.3.113 | 2 / 5 | |
| 0.3.112 | 2 / 5 | |
| 0.3.111 | 2 / 5 | |
| 0.3.110 | 2 / 5 | |
| 0.3.109 | 2 / 5 | |
| 0.3.108 | 2 / 5 | |
| 0.3.107 | 2 / 5 | |
| 0.3.106 | 2 / 5 | |
| 0.3.105 | 2 / 5 | |
| 0.3.104 | 2 / 5 | |
| 0.3.103 | 2 / 5 | |
| 0.3.102 | 2 / 5 | |
| 0.3.101 | 2 / 5 | |
| 0.3.100 | 2 / 5 | |
| 0.3.99 | 2 / 5 | |
| 0.3.98 | 2 / 5 | |
| 0.3.97 | 2 / 5 | |
| 0.3.96 | 2 / 5 | |
| 0.3.95 | 2 / 5 | |
| 0.3.94 | 2 / 5 | |
| 0.3.93 | 2 / 5 | |
| 0.3.92 | 2 / 5 | |
| 0.3.91 | 2 / 5 | |
| 0.3.90 | 2 / 5 | |
| 0.3.89 | 2 / 5 | |
| 0.3.88 | 2 / 5 | |
| 0.3.87 | 2 / 5 | |
| 0.3.86 | 2 / 5 | |
| 0.3.85 | 2 / 5 | |
| 0.3.84 | 2 / 5 | |
| 0.3.83 | 2 / 5 | |
| 0.3.82 | 2 / 5 | |
| 0.3.81 | 2 / 5 | |
| 0.3.80 | 2 / 5 | |
| 0.3.79 | 2 / 5 | |
| 0.3.78 | 2 / 5 | |
| 0.3.77 | 2 / 5 | |
| 0.3.76 | 2 / 5 |
v0.3.126
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.125
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.124
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.123
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.122
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.121
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.120
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.119
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.118
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.117
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.116
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.115
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.114
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.113
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.112
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.111
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.110
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.109
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.108
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.107
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.106
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.105
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.104
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.103
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.102
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.