@zibby/agent-workflow
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.32 | 4 / 4 | |
| 0.4.31 | 4 / 4 | |
| 0.4.30 | 4 / 4 | |
| 0.4.29 | 4 / 4 | |
| 0.4.28 | 4 / 4 | |
| 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.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.