@zowe/secrets-for-zowe-sdk
Credential management facilities for Imperative, Zowe CLI, and extenders.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Standard NAPI-RS prebuild check + fallback rebuild from source. Expected for native keyring bindings. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt native .node binaries for multiple platforms — standard NAPI-RS distribution pattern for native modules. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(join('..','lib','index.js')) uses only string literals; not truly dynamic. Stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Common for Zowe packages; no provenance is informational, not a risk signal for an established project. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.32.0 | 0 / 2 | |
| 8.29.4 | 0 / 2 | |
| 8.27.0 | 0 / 2 | |
| 8.24.2 | 0 / 2 |
v8.32.0
3 findingsScript: node scripts/prebuildCheck.js || npm run rebuild
Package contains compiled binaries that could be backdoors: • prebuilds/keyring.darwin-arm64.node • prebuilds/keyring.darwin-x64.node • prebuilds/keyring.linux-arm-gnueabihf.node • prebuilds/keyring.linux-arm64-gnu.node • prebuilds/keyring.linux-arm64-musl.node • prebuilds/keyring.linux-ia32-gnu.node • prebuilds/keyring.linux-x64-gnu.node • prebuilds/keyring.linux-x64-musl.node • prebuilds/keyring.win32-arm64-msvc.node • prebuilds/keyring.win32-ia32-msvc.node ... and 1 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.