@agentuity/pi — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

p0tofpiehuijirojhaynie

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Org-internal package with consistent publisher; missing gitHead likely reflects a CI/build environment change, not tampering.	ai	2026/06/04
publish-pattern	new-deps-added	AI (publish-pattern): @agentuity/server is a same-org sibling dep pinned to the same version; not a suspicious third-party addition.	ai	2026/06/02
bogus-package	bogus-package	AI (bogus-package): Internal monorepo plugin; sparse metadata is expected, not indicative of spam.	ai	2026/06/01
provenance	no-provenance	AI (provenance): Consistent pattern across this package's versions; no CI provenance configured.	ai	2026/06/01
phantom-deps	phantom-dep:@agentuity/aigateway	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly through @agentuity/adapter.	ai	2026/05/31
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @agentuity package; 'pi' refers to Pi coding agent integration, not a typosquat of 'pg'.	ai	2026/05/18
typosquat	typosquat.levenshtein:pino	AI (typosquat): Scoped @agentuity package; Levenshtein match is coincidental, not impersonation.	ai	2026/05/18
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @agentuity package; Levenshtein match is coincidental, not impersonation.	ai	2026/05/18
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @agentuity package; Levenshtein match is coincidental, not impersonation.	ai	2026/05/18
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped @agentuity package; Levenshtein match is coincidental, not impersonation.	ai	2026/05/18

Versions (showing 32 of 32)

Version	Deps	Published
3.0.5	3 / 4	2026-06-03
3.0.4	3 / 4	2026-06-03
3.0.3	3 / 4	2026-06-01
3.0.2	3 / 4	2026-05-29
3.0.1	3 / 4	2026-05-26
3.0.0	3 / 4	2026-05-25
2.0.26	2 / 4	2026-06-03
2.0.25	2 / 4	2026-06-01
2.0.24	2 / 4	2026-06-01
2.0.23	2 / 4	2026-05-29
2.0.22	2 / 4	2026-05-27
2.0.21	2 / 4	2026-05-13
2.0.20	2 / 4	2026-05-13
2.0.19	2 / 4	2026-05-12
2.0.18	2 / 4	2026-05-12
2.0.17	2 / 4	2026-05-09
2.0.16	2 / 4	2026-05-07
1.0.36	0 / 5	2026-03-06
1.0.35	0 / 5	2026-03-05
1.0.34	0 / 5	2026-03-04
1.0.33	0 / 5	2026-03-03
1.0.32	0 / 5	2026-03-03
1.0.31	0 / 5	2026-03-02
1.0.30	0 / 5	2026-03-02
1.0.29	0 / 5	2026-03-01
1.0.28	0 / 5	2026-03-01
1.0.27	0 / 5	2026-03-01
1.0.26	0 / 5	2026-02-28
1.0.25	0 / 5	2026-02-28
1.0.24	0 / 5	2026-02-26
1.0.23	0 / 5	2026-02-26
1.0.22	0 / 5	2026-02-25

v3.0.5

1 finding

INFO No provenance attestation provenance

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

v3.0.4

1 finding

INFO No provenance attestation provenance

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

v3.0.3

1 finding

INFO No provenance attestation provenance

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

v3.0.2

1 finding

INFO No provenance attestation provenance

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

v3.0.1

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: jhaynie → huijiro (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-05-26, but huijiro 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.

v3.0.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: jhaynie → huijiro (on 2026-05-25, known maintainer) provenance

This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-05-25, but huijiro 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.

v2.0.26

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

INFO No provenance attestation provenance

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

v2.0.25

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

INFO No provenance attestation provenance

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

v2.0.24

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

INFO No provenance attestation provenance

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

v2.0.23

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: huijiro.

LOW No provenance attestation provenance

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

v2.0.22

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: p0tofpie.

LOW No provenance attestation provenance

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

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

This version was published by a different npm account (p0tofpie) than the most recent previously approved version (huijiro) on 2026-05-27, but p0tofpie 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.

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.36

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.35

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.34

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.33

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.32

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.31

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.30

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.29

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.28

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.27

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.26

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.25

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.24

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.23

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.

v1.0.22

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@agentuity/pi' is 1 edit(s) away from popular package 'pg'.

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.