@mariozechner/pi-agent
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
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 2 / 3 | |
| 0.8.5 | 2 / 3 | |
| 0.8.4 | 2 / 3 | |
| 0.8.3 | 2 / 3 | |
| 0.8.2 | 2 / 3 | |
| 0.8.1 | 2 / 3 | |
| 0.8.0 | 2 / 3 | |
| 0.7.29 | 2 / 3 | |
| 0.7.28 | 2 / 3 | |
| 0.7.27 | 2 / 3 | |
| 0.7.26 | 2 / 3 | |
| 0.7.25 | 2 / 3 | |
| 0.7.24 | 2 / 3 | |
| 0.7.23 | 2 / 3 | |
| 0.7.22 | 2 / 3 | |
| 0.7.21 | 2 / 3 | |
| 0.7.20 | 2 / 3 | |
| 0.7.19 | 2 / 3 | |
| 0.7.18 | 2 / 3 | |
| 0.7.17 | 2 / 3 | |
| 0.7.16 | 2 / 3 | |
| 0.7.15 | 2 / 3 | |
| 0.7.13 | 2 / 3 | |
| 0.7.12 | 2 / 3 | |
| 0.7.11 | 2 / 3 | |
| 0.7.10 | 2 / 3 | |
| 0.7.9 | 2 / 3 | |
| 0.7.8 | 2 / 3 | |
| 0.7.7 | 2 / 3 | |
| 0.7.5 | 2 / 3 | |
| 0.7.4 | 2 / 3 | |
| 0.7.2 | 2 / 3 | |
| 0.7.1 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.6.2 | 2 / 3 | |
| 0.5.48 | 2 / 3 | |
| 0.5.47 | 2 / 3 | |
| 0.5.46 | 2 / 3 | |
| 0.5.45 | 2 / 3 | |
| 0.5.44 | 5 / 0 | |
| 0.5.43 | 5 / 0 | |
| 0.5.42 | 5 / 0 | |
| 0.5.41 | 5 / 0 | |
| 0.5.40 | 5 / 0 | |
| 0.5.39 | 5 / 0 | |
| 0.5.38 | 5 / 0 | |
| 0.5.35 | 5 / 0 | |
| 0.5.34 | 5 / 0 | |
| 0.5.33 | 5 / 0 | |
| 0.5.32 | 5 / 0 | |
| 0.5.31 | 5 / 0 |
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.