@t2000/sdk
TypeScript SDK for AI agent bank accounts on Sui — send, save, borrow, swap. NAVI lending + Cetus aggregator routing, sponsored gas, zkLogin compatible.
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/job-DXi8e8eA.d.ts | AI (source-diff): Bundled TS declaration file with long doc comments, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/job-DXi8e8eA.d.cts | AI (source-diff): Bundled TS declaration file with long doc comments, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/commerce-gxlqmkX7.d.ts | AI (source-diff): Long-line .d.ts type declarations from tsup build, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/commerce-gxlqmkX7.d.cts | AI (source-diff): Long-line .d.cts type declarations from tsup build, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/send-YAYf0YR3.d.cts | AI (source-diff): Long-line TS declaration file from tsup bundler, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/send-YAYf0YR3.d.ts | AI (source-diff): Same as .d.cts sibling — bundled type declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/commerce-DhJDA4Sq.d.cts | AI (source-diff): Bundled TS declaration file, long lines from type defs, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/commerce-DhJDA4Sq.d.ts | AI (source-diff): Bundled TS declaration file, long lines from type defs, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/job-CSq0DRsC.d.cts | AI (source-diff): Bundled TS declaration file with long doc comments, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/job-CSq0DRsC.d.ts | AI (source-diff): Bundled TS declaration file with long doc comments, not obfuscated code. | ai | |
| dependencies | unvetted-dep:@mppsui/mpp | AI (dependencies): Small DeFi-ecosystem dep matching package's stated Sui/DeFi purpose. | ai | |
| phantom-deps | phantom-dep:@suilend/sdk | AI (phantom-deps): Legit DeFi dependency likely used via bundled dist output; low risk profile. | ai | |
| source-diff | obfuscated-file:dist/send-D2nKpwJN.d.ts | AI (source-diff): Long-line trigger is a bundled TypeScript declaration file, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/send-D2nKpwJN.d.cts | AI (source-diff): Long-line trigger is a bundled TypeScript declaration file, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/job-BCRKTThm.d.ts | AI (source-diff): Long-line TS declaration file from tsup bundler, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/job-BCRKTThm.d.cts | AI (source-diff): Long-line TS declaration file from tsup bundler, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/commerce-CUGyTRcv.d.cts | AI (source-diff): Long-line trigger is a .d.cts type declaration file with verbose JSDoc, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/commerce-CUGyTRcv.d.ts | AI (source-diff): Same file emitted as .d.ts; readable TS types, false positive on line-length heuristic. | ai | |
| dependencies | unvetted-dep:@mysten/move-bytecode-template | AI (dependencies): Official Mysten Labs package, consistent with Sui SDK purpose. | ai | |
| source-diff | obfuscated-file:dist/commerce-D78r4-MZ.d.ts | AI (source-diff): TS declaration file with long doc comments, not minified/obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/commerce-D78r4-MZ.d.cts | AI (source-diff): TS declaration file with long doc comments, not minified/obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/send-DEK6aOGe.d.ts | AI (source-diff): Same .d.ts twin file, same tsup build artifact false positive. | ai | |
| source-diff | obfuscated-file:dist/send-DEK6aOGe.d.cts | AI (source-diff): Type declaration file with long lines from bundler; not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/send-CUUOLK_H.d.cts | AI (source-diff): TypeScript declaration file (.d.cts); long lines are bundled type rollup artifacts, not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/send-CUUOLK_H.d.ts | AI (source-diff): TypeScript declaration file (.d.ts); long lines are bundled type rollup artifacts, not executable obfuscated code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase driven by inlining the blake2b WASM binary; not injected payload. | ai | |
| source-diff | encoded-string-file:dist/adapters/index.js | AI (source-diff): Same blake2b WASM binary; benign cryptographic primitive bundled into dist. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Same blake2b WASM binary; benign cryptographic primitive bundled into dist. | ai | |
| phantom-deps | phantom-dep:@t2000/mpp-sui | AI (phantom-deps): Same-org scoped package; likely re-exported rather than directly imported in source. | ai | |
| source-diff | encoded-string-file:dist/adapters/index.cjs | AI (source-diff): Encoded string is a blake2b WASM binary bundled inline — standard cryptographic dependency, not malicious. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same blake2b WASM binary; benign cryptographic primitive bundled into dist. | ai | |
| phantom-deps | phantom-dep:mppx | AI (phantom-deps): Referenced in config/build files rather than direct imports; consistent with a build-time plugin pattern. | ai | |
| phantom-deps | phantom-dep:@naviprotocol/lending | AI (phantom-deps): @naviprotocol/lending is an explicit runtime dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pythnetwork/pyth-sui-js | AI (phantom-deps): Transitive/config dependency for Pyth oracle integration; consistent with SDK's DeFi purpose. | ai | |
| phantom-deps | phantom-dep:@suilend/sui-fe | AI (phantom-deps): Transitive/config dependency for Suilend integration; consistent with SDK's DeFi purpose. | ai | |
| provenance | no-provenance | AI (provenance): Package is an established SDK with 275 versions and a trusted publisher; lack of Sigstore provenance is a best-practice gap, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@zodios/core | AI (phantom-deps): @zodios/core is listed as a runtime dependency in package.json; phantom detection likely reflects indirect/config usage rather than a security issue. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@cetusprotocol/sui-clmm-sdk | AI (dependencies): @cetusprotocol/sui-clmm-sdk is the official Cetus Protocol CLMM SDK for Sui DeFi; its use is expected and appropriate for this DeFi/swap SDK. | ai |
Versions (showing 100 of 537)
| Version | Deps | Published |
|---|---|---|
| 10.6.0 | 13 / 7 | |
| 10.5.0 | 13 / 7 | |
| 10.3.1 | 12 / 7 | |
| 10.3.0 | 12 / 7 | |
| 10.2.0 | 12 / 7 | |
| 10.1.2 | 12 / 7 | |
| 10.1.1 | 12 / 7 | |
| 10.1.0 | 12 / 7 | |
| 10.0.0 | 12 / 7 | |
| 9.14.0 | 12 / 7 | |
| 9.13.0 | 12 / 7 | |
| 9.12.0 | 12 / 7 | |
| 9.11.0 | 12 / 7 | |
| 9.10.0 | 12 / 7 | |
| 9.9.1 | 12 / 7 | |
| 9.9.0 | 12 / 7 | |
| 9.7.1 | 12 / 7 | |
| 9.7.0 | 12 / 7 | |
| 9.6.0 | 12 / 7 | |
| 9.5.0 | 12 / 7 | |
| 9.4.0 | 12 / 7 | |
| 9.3.1 | 12 / 7 | |
| 9.3.0 | 12 / 7 | |
| 9.2.0 | 11 / 7 | |
| 9.1.0 | 11 / 7 | |
| 9.0.0 | 11 / 7 | |
| 8.2.0 | 11 / 7 | |
| 8.1.0 | 11 / 7 | |
| 8.0.2 | 11 / 7 | |
| 8.0.1 | 11 / 7 | |
| 8.0.0 | 11 / 7 | |
| 7.0.0 | 11 / 7 | |
| 6.0.0 | 11 / 7 | |
| 5.32.0 | 11 / 7 | |
| 5.31.0 | 11 / 7 | |
| 5.30.0 | 11 / 7 | |
| 5.29.0 | 11 / 7 | |
| 5.28.0 | 11 / 7 | |
| 5.27.0 | 11 / 7 | |
| 5.26.0 | 11 / 7 | |
| 5.25.0 | 11 / 7 | |
| 5.24.3 | 11 / 7 | |
| 5.24.2 | 11 / 7 | |
| 5.24.1 | 11 / 7 | |
| 5.24.0 | 11 / 7 | |
| 5.23.0 | 11 / 7 | |
| 5.22.0 | 11 / 7 | |
| 5.21.0 | 11 / 7 | |
| 5.20.1 | 11 / 7 | |
| 5.20.0 | 11 / 7 | |
| 5.19.0 | 10 / 7 | |
| 5.18.0 | 10 / 7 | |
| 5.17.0 | 8 / 7 | |
| 5.16.0 | 8 / 7 | |
| 5.15.1 | 8 / 7 | |
| 5.15.0 | 8 / 7 | |
| 5.14.3 | 8 / 7 | |
| 5.14.2 | 8 / 7 | |
| 5.14.1 | 8 / 7 | |
| 5.14.0 | 8 / 7 | |
| 5.13.0 | 8 / 7 | |
| 5.12.0 | 8 / 7 | |
| 5.11.0 | 8 / 7 | |
| 5.10.0 | 8 / 7 | |
| 5.9.0 | 8 / 7 | |
| 5.8.0 | 8 / 7 | |
| 5.7.3 | 8 / 7 | |
| 5.7.2 | 8 / 7 | |
| 5.7.1 | 8 / 7 | |
| 5.7.0 | 8 / 7 | |
| 5.6.1 | 8 / 7 | |
| 5.6.0 | 8 / 7 | |
| 5.5.1 | 8 / 7 | |
| 5.5.0 | 8 / 7 | |
| 5.4.0 | 8 / 7 | |
| 5.3.0 | 8 / 7 | |
| 5.2.0 | 8 / 7 | |
| 5.1.0 | 8 / 7 | |
| 5.0.0 | 9 / 7 | |
| 4.4.0 | 11 / 7 | |
| 4.3.1 | 11 / 7 | |
| 4.3.0 | 11 / 7 | |
| 4.2.2 | 11 / 7 | |
| 4.2.1 | 11 / 7 | |
| 4.2.0 | 11 / 7 | |
| 4.1.4 | 11 / 7 | |
| 4.1.3 | 11 / 7 | |
| 4.1.2 | 11 / 7 | |
| 4.1.1 | 11 / 7 | |
| 4.1.0 | 11 / 7 | |
| 4.0.2 | 11 / 7 | |
| 4.0.1 | 11 / 7 | |
| 4.0.0 | 11 / 7 | |
| 3.3.0 | 11 / 7 | |
| 3.2.0 | 11 / 7 | |
| 3.1.1 | 11 / 7 | |
| 3.1.0 | 11 / 7 | |
| 3.0.0 | 11 / 7 | |
| 2.20.3 | 11 / 7 | |
| 2.20.2 | 11 / 7 |
v10.6.0
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.
v10.5.0
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.
v10.3.1
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.
v10.3.0
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.
v10.2.0
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.
v10.1.2
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.
v10.1.1
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.
v10.1.0
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.
v10.0.0
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.
v9.14.0
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.
v9.13.0
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.
v9.12.0
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.
v9.11.0
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.
v9.10.0
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.
v9.9.1
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.
v9.9.0
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.
v9.7.1
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.
v9.7.0
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.
v9.6.0
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.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
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.
v9.3.0
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.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
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.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
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.
v5.15.1
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.
v5.15.0
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.
v5.14.3
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.
v5.14.2
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.
v5.14.1
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.
v5.14.0
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.
v5.13.0
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.
v5.12.0
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.
v5.11.0
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.
v5.10.0
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.
v5.9.0
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.
v5.8.0
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.
v5.7.3
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.
v5.7.2
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.
v5.7.1
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.
v5.7.0
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.
v5.6.1
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.
v5.6.0
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.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.