@voltagent/server-core
Framework-agnostic server core for VoltAgent
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/edge-eKW1ku2Y.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled type rollup; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/edge-eKW1ku2Y.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type rollup; not obfuscated code. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has strong track record (57 approved, 0 rejected); no code changes in this release; dormancy alone is not sufficient signal here. | ai | |
| source-diff | obfuscated-file:dist/edge-BdugtEoh.d.ts | AI (source-diff): Same as above — generated .d.ts bundle for edge export, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/edge-BdugtEoh.d.mts | AI (source-diff): Bundled TypeScript declaration file for edge export; long lines are normal for generated .d.ts bundles, not obfuscation. | ai | |
| dependencies | unvetted-dep:zod-from-json-schema-v3 | AI (dependencies): npm alias for zod-from-json-schema older version; intentional dual-version pattern, stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.1.17 | 8 / 3 | |
| 2.1.16 | 8 / 3 | |
| 2.1.15 | 8 / 3 | |
| 2.1.14 | 8 / 3 | |
| 2.1.12 | 8 / 3 | |
| 2.1.11 | 8 / 3 | |
| 2.1.9 | 8 / 3 | |
| 2.1.8 | 8 / 3 | |
| 2.1.7 | 8 / 3 | |
| 2.1.5 | 8 / 3 | |
| 2.1.4 | 8 / 3 | |
| 2.0.0 | 5 / 7 | |
| 1.0.36 | 8 / 3 | |
| 1.0.35 | 8 / 3 | |
| 1.0.32 | 8 / 3 | |
| 1.0.30 | 8 / 3 | |
| 1.0.29 | 8 / 3 | |
| 1.0.26 | 8 / 3 | |
| 1.0.25 | 8 / 3 | |
| 1.0.23 | 8 / 3 | |
| 1.0.21 | 8 / 3 |
v2.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.