@inkeep/agents-core
Agents Core contains the database schema, types, and validation schemas for Inkeep Agent Framework, along with core components.
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:ajv-formats | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nangohq/types | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-node | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-metrics | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-jaeger | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/baggage-span-processor | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-proto | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/auto-instrumentations-node | AI (phantom-deps): Declared and used; phantom-dep heuristic false positive for this package. | ai | |
| source-diff | net-exec-file:dist/node_modules/.pnpm/@[email protected]/node_modules/@vitest/snapshot/dist/index.js | AI (source-diff): File is bundled @vitest/snapshot test utility; VLQ/source-map code triggered the rule, not actual network+exec malware. | ai |
Versions (showing 19 of 125)
| Version | Deps | Published |
|---|---|---|
| 0.6.6 | 32 / 8 | |
| 0.6.5 | 32 / 8 | |
| 0.6.4 | 32 / 8 | |
| 0.6.0 | 32 / 8 | |
| 0.5.0 | 32 / 8 | |
| 0.3.0 | 30 / 8 | |
| 0.2.2 | 30 / 8 | |
| 0.2.1 | 28 / 8 | |
| 0.2.0 | 28 / 8 | |
| 0.1.10 | 28 / 8 | |
| 0.1.9 | 28 / 8 | |
| 0.1.8 | 28 / 8 | |
| 0.1.7 | 28 / 8 | |
| 0.1.6 | 28 / 7 | |
| 0.1.4 | 28 / 8 | |
| 0.1.3 | 28 / 8 | |
| 0.1.2 | 28 / 8 | |
| 0.1.1 | 28 / 8 | |
| 0.1.0 | 28 / 7 |
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.