@ag-ui/client
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to copilotkit org account is consistent with legitimate maintainer handoff; copilotkit has clean track record. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): Framework-scoped type package loaded by convention; expected pattern for TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@ag-ui/proto | AI (phantom-deps): Same-org scoped package in monorepo; convention-based loading is expected and stable. | ai | |
| phantom-deps | phantom-dep:@ag-ui/encoder | AI (phantom-deps): Same-org scoped package in monorepo; convention-based loading is expected and stable. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is legitimately used in config files; phantom-dep pattern is stable for this monorepo package. | ai | |
| phantom-deps | phantom-dep:untruncate-json | AI (phantom-deps): Referenced in config files; legitimate usage pattern for this package type. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Referenced in config files; legitimate usage pattern for this package type. | ai | |
| phantom-deps | phantom-dep:fast-json-patch | AI (phantom-deps): Referenced in config files; legitimate usage pattern for this package type. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.0.55 | 10 / 7 | |
| 0.0.54 | 10 / 7 | |
| 0.0.53 | 10 / 7 | |
| 0.0.52 | 10 / 7 | |
| 0.0.51 | 10 / 7 | |
| 0.0.50 | 10 / 7 | |
| 0.0.49 | 10 / 7 | |
| 0.0.48 | 10 / 7 | |
| 0.0.47 | 10 / 7 | |
| 0.0.46 | 10 / 7 | |
| 0.0.45 | 10 / 7 | |
| 0.0.44 | 10 / 6 | |
| 0.0.43 | 10 / 6 | |
| 0.0.42 | 10 / 6 | |
| 0.0.41 | 10 / 6 | |
| 0.0.40 | 9 / 6 | |
| 0.0.39 | 9 / 6 | |
| 0.0.38 | 9 / 6 | |
| 0.0.37 | 9 / 6 | |
| 0.0.36 | 9 / 6 | |
| 0.0.35 | 9 / 6 | |
| 0.0.34 | 9 / 6 | |
| 0.0.33 | 9 / 6 | |
| 0.0.32 | 9 / 6 | |
| 0.0.31 | 9 / 6 | |
| 0.0.30 | 9 / 6 | |
| 0.0.29 | 9 / 6 | |
| 0.0.28 | 9 / 6 | |
| 0.0.27 | 9 / 6 |
v0.0.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.54
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.53
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.52
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.