@ag-ui/proto
Protocol Buffer encoding/decoding for **Agent-User Interaction (AG-UI) Protocol** events.
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): Publisher change from _mme to copilotkit appears to be a legitimate transition to an org account; copilotkit has 4 approved packages, no rejected, and no malicious changes were introduced in this or surrounding versions. | ai | |
| phantom-deps | phantom-dep:@protobuf-ts/protoc | AI (phantom-deps): @protobuf-ts/protoc is a protobuf compiler tool used in the generate script for code generation, not imported at runtime. This phantom-dep pattern is expected and stable for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.0.55 | 3 / 7 | |
| 0.0.54 | 3 / 7 | |
| 0.0.53 | 3 / 7 | |
| 0.0.52 | 3 / 7 | |
| 0.0.51 | 3 / 7 | |
| 0.0.50 | 3 / 7 | |
| 0.0.49 | 3 / 7 | |
| 0.0.48 | 3 / 7 | |
| 0.0.47 | 3 / 7 | |
| 0.0.46 | 3 / 7 | |
| 0.0.45 | 3 / 7 | |
| 0.0.44 | 3 / 7 | |
| 0.0.43 | 3 / 7 | |
| 0.0.42 | 3 / 7 | |
| 0.0.41 | 3 / 7 | |
| 0.0.40 | 3 / 7 | |
| 0.0.39 | 3 / 7 | |
| 0.0.38 | 3 / 7 | |
| 0.0.37 | 3 / 7 | |
| 0.0.36 | 3 / 7 | |
| 0.0.35 | 2 / 7 | |
| 0.0.34 | 2 / 7 | |
| 0.0.33 | 2 / 7 | |
| 0.0.32 | 2 / 7 | |
| 0.0.31 | 2 / 7 | |
| 0.0.30 | 2 / 7 | |
| 0.0.29 | 2 / 7 | |
| 0.0.28 | 2 / 7 | |
| 0.0.27 | 2 / 7 |
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 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-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. 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.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. 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.43
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.42
2 findingsThis version was published by a different npm account than previous versions on 2025-12-05. 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.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.