@deepagents/evals
A general-purpose LLM evaluation framework with dataset loading, scoring, run persistence, model comparison, and console reporting.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ai-sdk/openai-compatible | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/groq | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/provider | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hono/vite-build | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@deepagents/agent | AI (phantom-deps): Same org scope; sibling monorepo package, stable false positive. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/vite | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@hono/vite-dev-server | AI (phantom-deps): Referenced in config files; bundled dep pattern for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.4.0 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 1.0.0 | 2 / 2 | |
| 0.39.0 | 2 / 2 | |
| 0.38.1 | 2 / 2 | |
| 0.38.0 | 2 / 2 | |
| 0.37.1 | 2 / 2 | |
| 0.37.0 | 2 / 2 | |
| 0.36.0 | 2 / 2 | |
| 0.35.0 | 2 / 2 | |
| 0.34.0 | 2 / 2 | |
| 0.33.0 | 2 / 2 | |
| 0.32.0 | 2 / 2 | |
| 0.31.0 | 2 / 2 | |
| 0.30.0 | 2 / 2 | |
| 0.29.1 | 2 / 2 | |
| 0.29.0 | 2 / 2 | |
| 0.28.0 | 2 / 2 | |
| 0.27.0 | 2 / 2 | |
| 0.26.0 | 2 / 2 | |
| 0.25.0 | 2 / 2 | |
| 0.24.0 | 2 / 2 | |
| 0.23.0 | 17 / 2 | |
| 0.22.0 | 17 / 2 | |
| 0.20.0 | 16 / 2 | |
| 0.19.0 | 16 / 2 |
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.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.
v0.20.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.
v0.19.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.