@t2000/engine
Agent engine for conversational finance — QueryEngine with 40 tools (29 read, 11 write), 9-guard runner, 7 skill recipes, silent intelligence layer, streaming, canvas. Chat-first by design — every write requires user confirmation.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@t2000/sdk | AI (dependencies): @t2000/sdk is an internal sibling package in the same monorepo scope; the unvetted signal is expected and stable for this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this publisher/scope; no other risk signals present to elevate this finding. | ai |
Versions (showing 100 of 303)
| Version | Deps | Published |
|---|---|---|
| 1.28.2 | 5 / 7 | |
| 1.28.1 | 5 / 7 | |
| 1.28.0 | 5 / 7 | |
| 1.27.2 | 5 / 7 | |
| 1.27.1 | 5 / 7 | |
| 1.27.0 | 5 / 7 | |
| 1.26.0 | 5 / 7 | |
| 1.25.3 | 5 / 7 | |
| 1.25.2 | 5 / 7 | |
| 1.25.1 | 5 / 7 | |
| 1.25.0 | 5 / 7 | |
| 1.24.14 | 5 / 7 | |
| 1.24.13 | 5 / 7 | |
| 1.24.12 | 5 / 7 | |
| 1.24.11 | 5 / 7 | |
| 1.24.10 | 5 / 7 | |
| 1.24.9 | 5 / 7 | |
| 1.24.8 | 5 / 7 | |
| 1.24.7 | 5 / 7 | |
| 1.24.6 | 5 / 7 | |
| 1.24.5 | 5 / 7 | |
| 1.24.3 | 5 / 7 | |
| 1.24.2 | 5 / 7 | |
| 1.24.1 | 5 / 7 | |
| 1.24.0 | 5 / 7 | |
| 1.23.1 | 5 / 7 | |
| 1.23.0 | 5 / 7 | |
| 1.22.2 | 5 / 7 | |
| 1.22.1 | 5 / 7 | |
| 1.22.0 | 5 / 7 | |
| 1.21.0 | 5 / 7 | |
| 1.20.0 | 5 / 7 | |
| 1.19.0 | 5 / 7 | |
| 1.18.0 | 5 / 7 | |
| 1.17.1 | 5 / 7 | |
| 1.17.0 | 5 / 7 | |
| 1.16.0 | 5 / 7 | |
| 1.15.1 | 5 / 7 | |
| 1.15.0 | 5 / 7 | |
| 1.14.0 | 5 / 7 | |
| 1.13.1 | 5 / 7 | |
| 1.13.0 | 5 / 7 | |
| 1.12.0 | 5 / 7 | |
| 1.11.4 | 5 / 7 | |
| 1.11.3 | 5 / 7 | |
| 1.11.2 | 5 / 7 | |
| 1.11.1 | 5 / 7 | |
| 1.11.0 | 5 / 7 | |
| 1.10.1 | 5 / 7 | |
| 1.10.0 | 5 / 7 | |
| 1.9.0 | 5 / 7 | |
| 1.8.0 | 5 / 7 | |
| 1.7.0 | 5 / 7 | |
| 1.6.0 | 5 / 7 | |
| 1.5.0 | 5 / 7 | |
| 1.4.0 | 5 / 7 | |
| 1.3.0 | 5 / 7 | |
| 1.2.1 | 5 / 7 | |
| 1.2.0 | 5 / 7 | |
| 1.1.2 | 5 / 7 | |
| 1.1.0 | 5 / 7 | |
| 1.0.1 | 5 / 7 | |
| 1.0.0 | 5 / 7 | |
| 0.56.2 | 5 / 7 | |
| 0.56.0 | 5 / 7 | |
| 0.55.0 | 5 / 7 | |
| 0.54.2 | 5 / 7 | |
| 0.54.1 | 5 / 7 | |
| 0.54.0 | 5 / 7 | |
| 0.53.4 | 5 / 7 | |
| 0.53.3 | 5 / 7 | |
| 0.53.2 | 5 / 7 | |
| 0.53.1 | 5 / 7 | |
| 0.53.0 | 5 / 7 | |
| 0.52.0 | 5 / 7 | |
| 0.51.1 | 5 / 7 | |
| 0.51.0 | 5 / 7 | |
| 0.50.3 | 5 / 7 | |
| 0.50.2 | 5 / 7 | |
| 0.50.1 | 5 / 7 | |
| 0.50.0 | 5 / 7 | |
| 0.49.0 | 5 / 7 | |
| 0.48.0 | 5 / 7 | |
| 0.47.1 | 5 / 7 | |
| 0.47.0 | 5 / 7 | |
| 0.46.16 | 5 / 7 | |
| 0.46.15 | 5 / 7 | |
| 0.46.14 | 5 / 7 | |
| 0.46.13 | 5 / 7 | |
| 0.46.12 | 5 / 7 | |
| 0.46.11 | 5 / 7 | |
| 0.46.10 | 5 / 7 | |
| 0.46.9 | 5 / 7 | |
| 0.46.8 | 5 / 7 | |
| 0.46.7 | 5 / 7 | |
| 0.46.6 | 5 / 7 | |
| 0.46.5 | 5 / 7 | |
| 0.46.4 | 5 / 7 | |
| 0.46.3 | 5 / 7 | |
| 0.46.2 | 5 / 7 |
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.