← Home

@frontmcp/plugins

npm Repository Homepage

FrontMCP plugins meta-package - installs all official plugins

6
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

davidfrontegg

Keywords

mcppluginsagentfrontfrontmcpframeworktypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@frontmcp/plugin-codecall AI (dependencies): First-party sibling package within the same org/version, not third-party unvetted code. ai
publish-pattern new-deps-added AI (publish-pattern): Meta-package restructuring to split into sibling plugin packages; expected pattern. ai

Versions (showing 6 of 6)

Version Deps Published
1.5.3 4 / 0
1.5.2 4 / 0
0.4.1 2 / 0
0.4.0 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0

v1.5.3

2 findings
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.

INFO Publisher changed: davidfrontegg → GitHub Actions (on 2026-07-18, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davidfrontegg) on 2026-07-18, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.5.2

2 findings
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.

INFO Publisher changed: davidfrontegg → GitHub Actions (on 2026-06-22, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (davidfrontegg) on 2026-06-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.