← Home

@fabriccode/cli

npm Repository Homepage

The AI coding agent built for the terminal. Generate code from natural language, automate tasks, and run terminal commands -- powered by 500+ AI models.

15
Versions
MIT
License
Yes
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

preddy4690

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @fabriccode/cli is not a typosquat of joi; Levenshtein match is spurious. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall selects platform-specific binary from optional deps — standard native binary distribution pattern. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in postinstall for binary selection; consistent with native binary distribution pattern. ai

Versions (showing 15 of 15)

Version Deps Published
7.0.116 0 / 0
7.0.115 0 / 0
7.0.114 0 / 0
7.0.90 0 / 0
7.0.76 0 / 0
7.0.75 0 / 0
7.0.73 0 / 0
7.0.65 0 / 0
7.0.64 0 / 0
7.0.63 0 / 0
7.0.62 0 / 0
7.0.58 0 / 0
7.0.50 0 / 0
7.0.49 0 / 0
7.0.48 0 / 0

v7.0.116

1 finding
LOW No provenance attestation provenance

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

v7.0.115

1 finding
LOW No provenance attestation provenance

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

v7.0.114

1 finding
LOW No provenance attestation provenance

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

v7.0.90

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.76

1 finding
LOW No provenance attestation provenance

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

v7.0.75

1 finding
LOW No provenance attestation provenance

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

v7.0.73

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.65

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.64

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.63

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.62

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.58

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.50

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.49

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.

v7.0.48

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: bun ./postinstall.mjs || node ./postinstall.mjs

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.