← Home

@zhivex-ai/bedrock

npm Repository Homepage

AWS Bedrock adapter for Zhivex AI SDK.

22
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mortiz.zhivex

Keywords

aisdkbedrockawstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Small new SDK package; lack of provenance is common and no other risk signals present. ai

Versions (showing 22 of 22)

Version Deps Published
0.5.6 3 / 0
0.5.5 3 / 0
0.5.4 2 / 0
0.5.3 2 / 0
0.5.2 2 / 0
0.5.1 2 / 0
0.5.0 2 / 0
0.4.5 2 / 0
0.4.4 2 / 0
0.4.3 2 / 0
0.4.2 2 / 0
0.4.1 2 / 0
0.4.0 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0
0.2.1 2 / 0
0.2.0 2 / 0
0.1.4 2 / 0
0.1.3 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0

v0.5.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.5

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: mortiz.zhivex → GitHub Actions (on 2026-07-19, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mortiz.zhivex) on 2026-07-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.5.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.