@deepagents/context
A domain-agnostic context system for LLM applications, including fragment rendering, persistence, chat orchestration, and portable sandbox tooling.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser.js | AI (source-diff): Bundled ESM output with source maps; readable identifiers, no eval/encoding. Long lines from bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Same as browser.js — bundled TypeScript with source maps, fully readable content. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/groq | AI (phantom-deps): Referenced in config/model definitions; phantom-dep heuristic misses indirect config usage. | ai | |
| phantom-deps | phantom-dep:@deepagents/agent | AI (phantom-deps): Same-org sibling package; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:stringcase | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package's usage pattern. | ai | |
| phantom-deps | phantom-dep:gpt-tokenizer | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package's usage pattern. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package's usage pattern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 15 / 6 | |
| 3.0.0 | 15 / 6 | |
| 2.4.0 | 15 / 5 | |
| 2.3.0 | 15 / 5 | |
| 2.2.0 | 15 / 5 | |
| 2.1.0 | 15 / 5 | |
| 0.6.0 | 3 / 1 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.