← Home

@zibby/agent-workflow

npm
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zibby

Keywords

aiworkflowgraphagentsorchestrationlanggraph

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Young internal package; lack of Sigstore provenance is a process gap, not a security signal for this package. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Bundled ESM package; imports resolved at build time, not via direct require(). ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): Bundled ESM package; imports resolved at build time, not via direct require(). ai
phantom-deps phantom-dep:handlebars AI (phantom-deps): Bundled ESM package; imports resolved at build time, not via direct require(). ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): Bundled ESM package; imports resolved at build time, not via direct require(). ai

Versions (showing 8 of 8)

Version Deps Published
0.4.5 4 / 4
0.4.3 4 / 4
0.4.1 4 / 4
0.3.2 4 / 4
0.3.1 4 / 4
0.3.0 4 / 4
0.1.4 4 / 4
0.1.3 4 / 4

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

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.

v0.4.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.

v0.3.2

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.

v0.3.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.

v0.3.0

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.

v0.1.4

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.

v0.1.3

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.