← Home

@polka-codes/workflow

npm
12
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

xlc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Bundled build; zod is a declared dep resolved at build time. ai
phantom-deps phantom-dep:@ai-sdk/provider AI (phantom-deps): Bundled build; @ai-sdk/provider is a declared dep resolved at build time. ai
phantom-deps phantom-dep:@ai-sdk/provider-utils AI (phantom-deps): Bundled build; @ai-sdk/provider-utils is a declared dep resolved at build time. ai
phantom-deps phantom-dep:ai AI (phantom-deps): Bundled build; ai is a declared dep resolved at build time, not directly imported in source. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): Bundled build; lodash-es is a declared dep resolved at build time. ai
bogus-package bogus-package AI (bogus-package): Tiny payload and missing metadata are normal for utility packages in scoped orgs. ai
phantom-deps phantom-dep:@polka-codes/core AI (phantom-deps): Same-org scoped dependency; monorepo pattern, not a real missing import. ai

Versions (showing 12 of 12)

Version Deps Published
0.9.52 5 / 0
0.9.51 5 / 0
0.9.50 5 / 0
0.9.49 5 / 0
0.9.48 5 / 0
0.9.47 5 / 0
0.9.46 6 / 1
0.9.45 1 / 0
0.9.44 1 / 0
0.9.43 1 / 0
0.9.42 1 / 0
0.9.41 1 / 0

v0.9.52

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.9.51

1 finding
LOW No provenance attestation provenance

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

v0.9.50

1 finding
LOW No provenance attestation provenance

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

v0.9.49

1 finding
LOW No provenance attestation provenance

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

v0.9.48

1 finding
LOW No provenance attestation provenance

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

v0.9.47

1 finding
LOW No provenance attestation provenance

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

v0.9.46

1 finding
LOW No provenance attestation provenance

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

v0.9.45

1 finding
LOW No provenance attestation provenance

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

v0.9.44

1 finding
LOW No provenance attestation provenance

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

v0.9.43

1 finding
LOW No provenance attestation provenance

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

v0.9.42

1 finding
LOW No provenance attestation provenance

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

v0.9.41

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.