← Home

vega-functions

1
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jheerdomoritzarvindsatya1hydrosqualllhermann

Keywords

vegaexpressionfunctions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:vega-time AI (dependencies): vega-time is a first-party Vega monorepo sub-package; not a suspicious dependency for vega-functions. ai
dependencies unvetted-dep:vega-scale AI (dependencies): vega-scale is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
dependencies unvetted-dep:vega-dataflow AI (dependencies): vega-dataflow is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
dependencies unvetted-dep:vega-expression AI (dependencies): vega-expression is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
dependencies unvetted-dep:vega-scenegraph AI (dependencies): vega-scenegraph is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
dependencies unvetted-dep:vega-selections AI (dependencies): vega-selections is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
dependencies unvetted-dep:vega-statistics AI (dependencies): vega-statistics is a first-party Vega monorepo sub-package; expected dependency for vega-functions. ai
provenance no-provenance AI (provenance): Vega packages predate Sigstore provenance; absence is expected and not a risk signal for this established ecosystem. ai

Versions (showing 1 of 1)

Version Deps Published
6.1.1 11 / 1

v6.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.