@ag-ui/encoder
Event encoding utilities for the **Agent-User Interaction (AG-UI) Protocol**.
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 (personal) to copilotkit (org) reflects a documented org migration for the AG-UI project; copilotkit has 4 approved packages and no rejections. | ai | |
| provenance | no-provenance | AI (provenance): The @ag-ui namespace is a legitimate monorepo project; lack of Sigstore provenance is common and not a risk indicator for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.0.55 | 2 / 6 | |
| 0.0.54 | 2 / 6 | |
| 0.0.53 | 2 / 6 | |
| 0.0.52 | 2 / 6 | |
| 0.0.51 | 2 / 6 | |
| 0.0.50 | 2 / 6 | |
| 0.0.49 | 2 / 6 | |
| 0.0.48 | 2 / 6 | |
| 0.0.47 | 2 / 6 | |
| 0.0.46 | 2 / 6 | |
| 0.0.45 | 2 / 6 | |
| 0.0.44 | 2 / 5 | |
| 0.0.43 | 2 / 5 | |
| 0.0.42 | 2 / 5 | |
| 0.0.41 | 2 / 5 | |
| 0.0.40 | 2 / 5 | |
| 0.0.39 | 2 / 5 | |
| 0.0.38 | 2 / 5 | |
| 0.0.37 | 2 / 5 | |
| 0.0.36 | 2 / 5 | |
| 0.0.35 | 2 / 5 | |
| 0.0.34 | 2 / 5 | |
| 0.0.33 | 2 / 5 | |
| 0.0.32 | 2 / 5 | |
| 0.0.31 | 2 / 5 | |
| 0.0.30 | 2 / 5 | |
| 0.0.29 | 2 / 5 | |
| 0.0.28 | 2 / 5 | |
| 0.0.27 | 2 / 5 |
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 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package 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.
[Accepted risk] 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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.