@the-forge-flow/tff-cc MIT 20 versions

@the-forge-flow/tff-cc

npm Repository

Autonomous coding agent orchestrator for Claude Code

20

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

the-forge-flow-ai

Keywords

claude-codeplannotatororchestration

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): Binaries are better-sqlite3 prebuilt native modules matching the declared runtime dependency; standard distribution pattern.	ai	2026/05/25
semgrep	semgrep:env-bulk-read	AI (semgrep): Used to sanitize git environment variables; reads env to filter non-GIT_ keys, not to exfiltrate.	ai	2026/05/25
semgrep	semgrep:hex-decode	AI (semgrep): UUID string to bytes conversion; no payload hiding, purely data transformation.	ai	2026/05/25

Versions (showing 20 of 20)

Version	Deps	Published
0.9.26	1 / 17	2026-05-09
0.9.25	1 / 17	2026-05-03
0.9.24	1 / 17	2026-05-02
0.9.23	1 / 17	2026-05-01
0.9.22	1 / 17	2026-05-01
0.9.21	1 / 17	2026-05-01
0.9.20	1 / 17	2026-04-30
0.9.19	1 / 17	2026-04-30
0.9.17	1 / 17	2026-04-30
0.9.16	1 / 17	2026-04-29
0.9.15	1 / 17	2026-04-25
0.9.14	1 / 17	2026-04-25
0.9.13	1 / 17	2026-04-24
0.9.12	1 / 17	2026-04-24
0.9.11	1 / 17	2026-04-23
0.9.10	1 / 17	2026-04-22
0.9.9	1 / 13	2026-04-20
0.9.8	1 / 14	2026-04-20
0.9.7	1 / 14	2026-04-19
0.9.6	1 / 14	2026-04-18

v0.9.26

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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

2 findings

HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • native/better_sqlite3.darwin-arm64.node • native/better_sqlite3.darwin-x64.node • native/better_sqlite3.linux-arm64.node • native/better_sqlite3.linux-x64.node • native/better_sqlite3.win32-x64.node

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.