← Home

@opentabs-dev/plugin-sdk

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

opentabs-dev-admin

Keywords

opentabsmcpmodelcontextprotocolai-agentbrowserchrome-extensionplugin-sdkopentabs-plugin

Versions (showing 34 of 34)

Version Deps Published
0.0.115 1 / 2
0.0.109 1 / 2
0.0.108 1 / 2
0.0.107 1 / 2
0.0.106 1 / 2
0.0.105 1 / 2
0.0.104 1 / 2
0.0.103 1 / 2
0.0.102 1 / 2
0.0.101 1 / 2
0.0.100 1 / 2
0.0.99 1 / 2
0.0.98 1 / 2
0.0.97 1 / 2
0.0.96 1 / 2
0.0.95 1 / 2
0.0.94 1 / 2
0.0.93 1 / 2
0.0.92 1 / 2
0.0.91 1 / 2
0.0.90 1 / 2
0.0.89 1 / 2
0.0.88 1 / 2
0.0.87 1 / 2
0.0.86 1 / 2
0.0.85 1 / 2
0.0.84 1 / 2
0.0.7 1 / 1
0.0.6 1 / 1
0.0.5 1 / 1
0.0.4 1 / 1
0.0.3 1 / 1
0.0.2 1 / 1
0.0.1 1 / 1

v0.0.115

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: opentabs-dev-admin → GitHub Actions (on 2026-07-27, 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 (opentabs-dev-admin) on 2026-07-27, 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.