@ifi/oh-pi
One-click setup for pi-coding-agent — extensions, themes, prompts, skills, and ant-colony swarm. Like oh-my-zsh for pi.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:node_modules/croner/dist/croner.js | AI (source-diff): Standard minified dist bundle from the croner npm package; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:node_modules/croner/dist/croner.cjs | AI (source-diff): Standard minified dist bundle from the croner npm package; not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-skills | AI (phantom-deps): Same as above — pi config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-themes | AI (phantom-deps): Same as above — pi config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-ant-colony | AI (phantom-deps): Same as above — pi config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-extensions | AI (phantom-deps): Same as above — pi config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-prompts | AI (phantom-deps): Same as above — pi config path reference, not a JS import. | ai | |
| phantom-deps | phantom-dep:@ifi/oh-pi-agents | AI (phantom-deps): Deps are consumed via pi config path references, not JS imports; phantom-dep is a stable false positive for this meta-package. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @ifi/oh-pi is unrelated to hapi; name derives from oh-my-zsh convention for pi-coding-agent tooling. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 1 / 0 | |
| 0.5.0 | 9 / 0 | |
| 0.4.4 | 9 / 0 | |
| 0.4.2 | 9 / 0 | |
| 0.4.1 | 9 / 0 | |
| 0.4.0 | 9 / 0 | |
| 0.3.6 | 9 / 0 | |
| 0.3.5 | 9 / 0 | |
| 0.3.4 | 9 / 0 | |
| 0.3.3 | 9 / 0 | |
| 0.3.2 | 9 / 0 | |
| 0.3.1 | 9 / 0 | |
| 0.3.0 | 9 / 0 | |
| 0.2.16 | 9 / 0 | |
| 0.2.15 | 9 / 0 | |
| 0.2.14 | 9 / 0 | |
| 0.2.12 | 6 / 0 | |
| 0.2.11 | 7 / 0 | |
| 0.2.10 | 6 / 0 | |
| 0.2.9 | 6 / 0 | |
| 0.2.8 | 6 / 0 | |
| 0.2.7 | 6 / 0 | |
| 0.2.4 | 6 / 0 | |
| 0.2.3 | 6 / 0 | |
| 0.2.1 | 6 / 0 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.