@jay-framework/webmcp-plugin
WebMCP plugin for jay-stack — automatically exposes page interactions as WebMCP tools, resources, and prompts
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @jay-framework packages; not a risk indicator for this publisher. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 2 / 8 | |
| 0.17.4 | 2 / 8 | |
| 0.17.3 | 2 / 8 | |
| 0.17.2 | 2 / 8 | |
| 0.17.1 | 2 / 8 | |
| 0.17.0 | 2 / 8 | |
| 0.16.5 | 2 / 8 | |
| 0.16.4 | 2 / 8 | |
| 0.16.3 | 2 / 8 | |
| 0.16.2 | 2 / 8 | |
| 0.16.1 | 2 / 8 | |
| 0.16.0 | 2 / 8 | |
| 0.15.6 | 2 / 8 | |
| 0.15.5 | 2 / 8 | |
| 0.15.4 | 2 / 8 | |
| 0.15.3 | 2 / 8 | |
| 0.15.2 | 2 / 8 | |
| 0.15.1 | 2 / 8 | |
| 0.15.0 | 2 / 8 | |
| 0.14.0 | 2 / 8 | |
| 0.13.0 | 2 / 8 | |
| 0.12.0 | 2 / 8 |
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
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.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.