@agentuity/aigateway
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publisher has strong track record; likely a CI/build environment change within the same org, not a supply chain indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is a style issue, not a malware signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @agentuity/server, a same-org sibling at matching version — not a third-party supply-chain risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package; missing metadata is expected for private/org-scoped packages. | ai | |
| provenance | no-provenance | AI (provenance): Org package published via bun; no provenance is consistent across versions. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 3.1.14 | 5 / 4 | |
| 3.1.13 | 5 / 4 | |
| 3.1.12 | 5 / 4 | |
| 3.1.11 | 5 / 4 | |
| 3.1.10 | 5 / 4 | |
| 3.1.9 | 5 / 4 | |
| 3.1.8 | 5 / 4 | |
| 3.1.7 | 4 / 4 | |
| 3.1.6 | 4 / 4 | |
| 3.1.5 | 4 / 4 | |
| 3.1.4 | 4 / 4 | |
| 3.1.3 | 4 / 4 | |
| 3.1.2 | 4 / 4 | |
| 3.1.1 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.12 | 3 / 4 | |
| 3.0.11 | 3 / 4 | |
| 3.0.10 | 3 / 4 | |
| 3.0.9 | 3 / 4 | |
| 3.0.8 | 3 / 4 | |
| 3.0.7 | 3 / 4 | |
| 3.0.6 | 3 / 4 | |
| 3.0.5 | 3 / 4 | |
| 3.0.4 | 3 / 4 | |
| 3.0.3 | 3 / 4 | |
| 3.0.2 | 3 / 4 | |
| 3.0.1 | 3 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.0.30 | 3 / 4 | |
| 2.0.29 | 3 / 4 | |
| 2.0.28 | 3 / 4 | |
| 2.0.27 | 3 / 4 | |
| 2.0.26 | 3 / 4 | |
| 2.0.25 | 3 / 4 | |
| 2.0.24 | 3 / 4 | |
| 2.0.23 | 3 / 4 | |
| 2.0.22 | 3 / 4 | |
| 2.0.21 | 3 / 4 | |
| 2.0.20 | 3 / 4 | |
| 2.0.19 | 3 / 4 | |
| 2.0.18 | 3 / 4 | |
| 2.0.17 | 3 / 4 | |
| 2.0.16 | 3 / 4 | |
| 2.0.15 | 3 / 4 |
v3.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-20, but jhaynie 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.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-06, but jhaynie 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.1.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-07-03, 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.1.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhaynie) than the most recent previously approved version (huijiro) on 2026-07-02, but jhaynie 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.1.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (huijiro) than the most recent previously approved version (p0tofpie) on 2026-06-29, 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.