@uniswap/ai-toolkit-nx-claude
This package provides Nx generators for installing Claude Code addon MCP servers. It also includes the `claude-plus` script for enhanced Claude Code startup.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.5.37 | 2 / 0 | |
| 0.5.36 | 2 / 0 | |
| 0.5.35 | 2 / 0 | |
| 0.5.34 | 2 / 0 | |
| 0.5.33 | 2 / 0 | |
| 0.5.32 | 2 / 0 | |
| 0.5.31 | 2 / 0 | |
| 0.5.30 | 2 / 0 | |
| 0.5.29 | 2 / 2 | |
| 0.5.28 | 2 / 2 | |
| 0.5.27 | 2 / 2 | |
| 0.5.26 | 2 / 2 | |
| 0.5.25 | 2 / 2 | |
| 0.5.24 | 2 / 2 | |
| 0.5.23 | 2 / 2 | |
| 0.5.22 | 2 / 2 | |
| 0.5.21 | 2 / 2 | |
| 0.5.20 | 2 / 2 | |
| 0.5.19 | 2 / 2 | |
| 0.5.18 | 2 / 2 | |
| 0.5.17 | 2 / 2 | |
| 0.5.16 | 2 / 2 | |
| 0.5.15 | 2 / 2 | |
| 0.5.14 | 2 / 2 | |
| 0.5.13 | 2 / 2 | |
| 0.5.12 | 2 / 2 | |
| 0.5.9 | 2 / 2 | |
| 0.5.8 | 2 / 2 | |
| 0.5.7 | 2 / 2 |
v0.5.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.