@tangle-network/sandbox
Client SDK for the Tangle Sandbox platform - build AI agent applications with dev containers
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/types-DtbMtW0q.d.ts | AI (source-diff): Generated bundled type declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/sandbox-B6qbvsur.d.ts | AI (source-diff): Bundled type-declaration file with long lines, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/types-Cmpv-ox_.d.ts | AI (source-diff): Bundled .d.ts type declarations with long lines, not code obfuscation. | ai | |
| source-diff | obfuscated-file:dist/sandbox-C2x9Yumw.d.ts | AI (source-diff): Bundled/minified type declarations, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/sandbox-Bm2C9Phd.d.ts | AI (source-diff): Long-line .d.ts type declarations from bundler, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/sandbox-DcOyvnIy.d.ts | AI (source-diff): Bundled/minified TypeScript declaration file, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-C4dFf5eL.d.ts | AI (source-diff): Bundled TypeScript declaration file, not true obfuscation; no malicious behavior. | ai | |
| provenance | missing-githead | AI (provenance): Minor publish-metadata regression from a trusted, established publisher. | ai | |
| source-diff | obfuscated-file:dist/types-BGGfKALh.d.ts | AI (source-diff): Long-line bundled .d.ts type file, not code obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-BvSoEHz8.d.ts | AI (source-diff): Minified bundled type declarations, not true obfuscation; no malicious behavior. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publish account switch, provenance direction unchanged vs prior approved. | ai | |
| source-diff | obfuscated-file:dist/types-D2C72ySk.d.ts | AI (source-diff): Bundled type declarations from tsdown build, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/sandbox-B55j2q9K.d.ts | AI (source-diff): File is a bundled TypeScript declaration with long import lines, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/sandbox-aBpWqler.d.ts | AI (source-diff): TypeScript .d.ts declaration file with long type lines from tsdown bundler; not obfuscated. | ai | |
| phantom-deps | phantom-dep:@tangle-network/cli-agent-registry | AI (phantom-deps): Same-org dep declared but not directly imported; consistent with optional/re-exported dependency pattern for this SDK. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 3 / 14 | |
| 0.11.1 | 2 / 11 | |
| 0.11.0 | 2 / 11 | |
| 0.10.5 | 2 / 10 | |
| 0.10.4 | 2 / 10 | |
| 0.10.3 | 2 / 10 | |
| 0.10.2 | 2 / 10 | |
| 0.10.1 | 2 / 10 | |
| 0.10.0 | 2 / 10 | |
| 0.9.7 | 2 / 10 | |
| 0.9.6 | 2 / 10 | |
| 0.9.5 | 2 / 10 | |
| 0.9.4 | 2 / 10 | |
| 0.9.3 | 2 / 10 | |
| 0.2.1 | 1 / 10 | |
| 0.1.2 | 0 / 7 | |
| 0.1.1 | 0 / 7 | |
| 0.1.0 | 1 / 7 | |
| 0.0.3 | 0 / 8 |
v0.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drewstone) than the most recent previously approved version (GitHub Actions) on 2026-07-27, but drewstone is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.11.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.11.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.10.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: drewstone.
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.
v0.10.4
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-13. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.10.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: drewstone.
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.
v0.10.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: drewstone.
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.
v0.10.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: drewstone.
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.
v0.10.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.9.7
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.9.6
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.9.5
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-28. This could indicate a legitimate maintainer transition or an account compromise.
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.
v0.9.4
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-27. This could indicate a legitimate maintainer transition or an account compromise.
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.