← Home

@ai-sdk/mcp

npm Repository Homepage
64
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

vercel-release-botmatheussmatt.straka

Keywords

aimcp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Vercel AI SDK migrated publishing to GitHub Actions CI with SLSA attestation; this is a documented infra change, not a compromise. ai
typosquat typosquat.levenshtein:yup AI (typosquat): False positive: @ai-sdk/mcp is a scoped Vercel AI SDK package with no relation to the 'yup' validation library. The Levenshtein match is coincidental. ai

Versions (showing 64 of 64)

Version Deps Published
1.0.46 3 / 7
1.0.45 3 / 7
1.0.44 3 / 7
1.0.43 3 / 7
1.0.42 3 / 7
1.0.41 3 / 7
1.0.40 3 / 7
1.0.39 3 / 7
1.0.38 3 / 7
1.0.37 3 / 7
1.0.36 3 / 7
1.0.35 3 / 7
1.0.34 3 / 7
1.0.33 3 / 7
1.0.32 3 / 7
1.0.31 3 / 7
1.0.30 3 / 7
1.0.29 3 / 7
1.0.28 3 / 7
1.0.27 3 / 7
1.0.26 3 / 7
1.0.25 3 / 7
1.0.24 3 / 7
1.0.23 3 / 7
1.0.22 3 / 7
1.0.21 3 / 7
1.0.20 3 / 7
1.0.19 3 / 7
1.0.18 3 / 7
1.0.17 3 / 7
1.0.16 3 / 7
1.0.15 3 / 7
1.0.14 3 / 7
1.0.13 3 / 7
1.0.12 3 / 7
1.0.11 3 / 7
1.0.10 3 / 7
1.0.9 3 / 7
1.0.8 3 / 7
1.0.7 3 / 7
1.0.6 3 / 7
1.0.5 3 / 7
1.0.4 3 / 7
1.0.3 3 / 7
1.0.2 3 / 7
1.0.1 3 / 7
1.0.0 3 / 7
0.0.18 3 / 7
0.0.17 3 / 7
0.0.16 3 / 7
0.0.15 3 / 7
0.0.14 3 / 7
0.0.13 3 / 7
0.0.12 3 / 7
0.0.11 3 / 7
0.0.10 3 / 6
0.0.9 3 / 6
0.0.8 3 / 6
0.0.7 3 / 6
0.0.6 3 / 5
0.0.5 3 / 5
0.0.4 3 / 5
0.0.3 3 / 5
0.0.2 3 / 5

v1.0.46

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.45

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.44

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.43

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.42

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.41

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.40

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.39

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.38

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.37

2 findings
HIGH Publisher changed: vercel-release-bot → GitHub Actions (on 2026-04-29) provenance

This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.18

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.17

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.