@browserstack/mcp-server
BrowserStack's Official MCP Server
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Config-referenced logging dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Config-referenced HTTP client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-referenced environment loader; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Config-referenced logging formatter; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/form-data | AI (phantom-deps): Framework-scoped TypeScript types; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:browserstack-local | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Config-referenced core SDK; stable pattern for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.2.20 | 13 / 11 | |
| 1.2.19 | 13 / 11 | |
| 1.2.18 | 13 / 11 | |
| 1.2.17 | 13 / 11 | |
| 1.2.16 | 13 / 11 | |
| 1.2.14 | 13 / 11 | |
| 1.2.8 | 13 / 11 | |
| 1.2.7 | 13 / 11 | |
| 1.2.6 | 13 / 11 | |
| 1.2.5 | 13 / 11 | |
| 1.2.4 | 13 / 11 | |
| 1.2.3 | 13 / 11 | |
| 1.2.2 | 13 / 11 | |
| 1.2.1 | 13 / 11 | |
| 1.2.0 | 13 / 11 | |
| 1.1.9 | 13 / 11 | |
| 1.1.8 | 13 / 11 | |
| 1.1.7 | 13 / 11 | |
| 1.1.6 | 13 / 11 | |
| 1.1.5 | 13 / 11 | |
| 1.1.4 | 13 / 11 | |
| 1.1.3 | 13 / 11 | |
| 1.1.2 | 13 / 11 | |
| 1.1.1 | 13 / 11 | |
| 1.1.0 | 13 / 11 | |
| 1.0.15 | 13 / 11 | |
| 1.0.14 | 12 / 10 | |
| 1.0.13 | 9 / 10 | |
| 1.0.12 | 9 / 10 | |
| 1.0.11 | 9 / 10 | |
| 1.0.10 | 9 / 10 | |
| 1.0.9 | 9 / 10 | |
| 1.0.8 | 9 / 10 | |
| 1.0.6 | 9 / 10 | |
| 1.0.5 | 9 / 10 |
v1.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.