← Home

@ifi/oh-pi-cli

npm Repository Homepage

Interactive TUI configurator for pi-coding-agent.

25
Versions
MIT
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

ifiokjr

Keywords

cliconfigurationinstalleroh-pipipi-coding-agenttui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ifi/pi-plan AI (phantom-deps): Same-org monorepo dep; bundled CLI pattern, not a real phantom. ai
phantom-deps phantom-dep:@ifi/pi-spec AI (phantom-deps): Same-org monorepo dep; bundled CLI pattern, not a real phantom. ai
phantom-deps phantom-dep:@ifi/pi-shared-qna AI (phantom-deps): Same-org monorepo dep; bundled CLI pattern, not a real phantom. ai
phantom-deps phantom-dep:@ifi/pi-extension-subagents AI (phantom-deps): Same-org monorepo dep; bundled CLI pattern, not a real phantom. ai
phantom-deps phantom-dep:@ifi/oh-pi-ant-colony AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai
phantom-deps phantom-dep:@ifi/oh-pi-agents AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai
phantom-deps phantom-dep:@ifi/oh-pi-extensions AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai
phantom-deps phantom-dep:@ifi/oh-pi-skills AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai
phantom-deps phantom-dep:@ifi/oh-pi-themes AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai
phantom-deps phantom-dep:@ifi/oh-pi-prompts AI (phantom-deps): Same-org monorepo sibling; likely re-exported via index, not directly imported. ai

Versions (showing 25 of 25)

Version Deps Published
0.5.1 13 / 0
0.5.0 13 / 0
0.4.4 13 / 0
0.4.2 13 / 0
0.4.1 13 / 0
0.4.0 13 / 0
0.3.6 13 / 0
0.3.5 13 / 0
0.3.4 13 / 0
0.3.3 13 / 0
0.3.2 13 / 0
0.3.1 13 / 0
0.3.0 13 / 0
0.2.16 13 / 0
0.2.15 13 / 0
0.2.14 10 / 0
0.2.12 9 / 0
0.2.11 9 / 0
0.2.10 9 / 0
0.2.9 9 / 0
0.2.8 9 / 0
0.2.7 9 / 0
0.2.4 9 / 0
0.2.3 9 / 0
0.2.1 9 / 0

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.15

1 finding
LOW No provenance attestation provenance

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

v0.2.14

1 finding
LOW No provenance attestation provenance

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

v0.2.12

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

1 finding
LOW No provenance attestation provenance

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

v0.2.10

1 finding
LOW No provenance attestation provenance

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

v0.2.9

1 finding
LOW No provenance attestation provenance

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

v0.2.8

1 finding
LOW No provenance attestation provenance

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

v0.2.7

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

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

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