@opentabs-dev/mcp-server
MCP server that turns browser tabs into AI agent tools via a Chrome extension plugin system
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is `open` v11, a canonical npm package for browser/file launching; fits the package's browser-tab purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped private package (@opentabs-dev); missing repo/keywords/description is expected for internal tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; no description is consistent across its 90 published versions. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.0.109 | 7 / 1 | |
| 0.0.108 | 7 / 1 | |
| 0.0.107 | 7 / 1 | |
| 0.0.106 | 7 / 1 | |
| 0.0.105 | 7 / 1 | |
| 0.0.104 | 7 / 1 | |
| 0.0.103 | 7 / 1 | |
| 0.0.102 | 7 / 1 | |
| 0.0.101 | 7 / 1 | |
| 0.0.100 | 7 / 1 | |
| 0.0.99 | 7 / 1 | |
| 0.0.98 | 7 / 1 | |
| 0.0.97 | 7 / 1 | |
| 0.0.96 | 7 / 1 | |
| 0.0.95 | 7 / 1 | |
| 0.0.94 | 7 / 1 | |
| 0.0.93 | 7 / 1 | |
| 0.0.92 | 7 / 1 | |
| 0.0.91 | 7 / 1 | |
| 0.0.90 | 7 / 1 | |
| 0.0.89 | 7 / 1 | |
| 0.0.88 | 7 / 1 | |
| 0.0.87 | 7 / 1 | |
| 0.0.86 | 7 / 1 | |
| 0.0.85 | 7 / 1 | |
| 0.0.84 | 7 / 1 | |
| 0.0.83 | 7 / 1 | |
| 0.0.82 | 6 / 1 | |
| 0.0.81 | 6 / 1 | |
| 0.0.64 | 5 / 1 | |
| 0.0.63 | 5 / 1 | |
| 0.0.62 | 5 / 1 | |
| 0.0.61 | 5 / 1 | |
| 0.0.60 | 5 / 1 | |
| 0.0.59 | 5 / 1 | |
| 0.0.58 | 5 / 1 | |
| 0.0.57 | 5 / 1 | |
| 0.0.56 | 5 / 1 | |
| 0.0.55 | 5 / 1 | |
| 0.0.54 | 5 / 1 | |
| 0.0.53 | 5 / 1 | |
| 0.0.52 | 5 / 1 | |
| 0.0.51 | 5 / 1 | |
| 0.0.50 | 5 / 1 | |
| 0.0.49 | 5 / 1 | |
| 0.0.48 | 5 / 1 | |
| 0.0.47 | 5 / 1 | |
| 0.0.46 | 5 / 1 | |
| 0.0.45 | 5 / 1 | |
| 0.0.44 | 5 / 1 | |
| 0.0.43 | 5 / 1 |
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: opentabs-dev-admin.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.