@mastra/agent-browser
Browser automation for Mastra agents using agent-browser
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation provides stronger supply chain integrity than gitHead; acceptable for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Part of mastra-ai monorepo; 0.0.0 is a standard initial release pattern for this publisher's packages. | ai | |
| phantom-deps | phantom-dep:typed-emitter | AI (phantom-deps): typed-emitter is a declared runtime dep used for type-level event emitter definitions; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 1 / 13 | |
| 0.2.2 | 1 / 13 | |
| 0.2.1 | 2 / 13 | |
| 0.2.0 | 2 / 13 | |
| 0.1.0 | 2 / 12 | |
| 0.0.0 | 2 / 12 |
v0.3.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.2.2
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.