← Home

@earendil-works/pi-ai

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mitsuhikobadlogicrwachtler

Keywords

aillmopenaianthropicgeminibedrockunifiedapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:chalk AI (phantom-deps): Build/config tool; stable false positive for this package. ai
phantom-deps phantom-dep:undici AI (phantom-deps): Implicit Node.js runtime dependency; stable false positive. ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): Config/build reference; stable false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.76.0 10 / 3
0.75.5 10 / 3
0.75.4 9 / 3
0.75.3 9 / 3
0.75.2 9 / 3
0.75.1 9 / 3
0.75.0 9 / 3
0.74.2 9 / 3
0.74.1 9 / 3
0.74.0 11 / 3

v0.76.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: badlogic → mitsuhiko (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (mitsuhiko) than the most recent previously approved version (badlogic) on 2026-05-27, but mitsuhiko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.75.5

1 finding
LOW No provenance attestation provenance

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

v0.75.4

1 finding
LOW No provenance attestation provenance

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

v0.75.3

1 finding
LOW No provenance attestation provenance

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

v0.75.2

1 finding
LOW No provenance attestation provenance

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

v0.75.1

1 finding
LOW No provenance attestation provenance

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

v0.75.0

1 finding
LOW No provenance attestation provenance

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

v0.74.2

1 finding
LOW No provenance attestation provenance

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

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