@executor-js/plugin-onepassword
[1Password](https://1password.com) integration for the executor. Provides a secret source that resolves values from a 1Password vault, backed by either the desktop app (connect.sock) or a service account token.
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with the original maintainer's repo. | ai | |
| phantom-deps | phantom-dep:@executor/api | AI (phantom-deps): Declared as dep and referenced in config files; phantom-dep heuristic false positive for this plugin package. | ai | |
| phantom-deps | phantom-dep:@effect-atom/atom-react | AI (phantom-deps): Optional peer dep referenced in config; not directly imported by design — stable false positive. | ai | |
| phantom-deps | phantom-dep:@effect/atom-react | AI (phantom-deps): Declared as optional peer dependency; not expected to be directly imported in the plugin itself. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.4.28 | 5 / 7 | |
| 1.4.20 | 5 / 7 | |
| 0.1.0 | 5 / 7 | |
| 0.0.2 | 5 / 7 | |
| 0.0.1 | 7 / 6 |
v1.4.28
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.20
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.