← Home

machinepack-redis

npm Repository Homepage

Structured Node.js bindings for Redis.

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

rachaelshawmikermcneileashaw

Keywords

Redismachinesmachinepack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): eashaw is a Sails Company contributor with 856 approved packages; transition from rachaelshaw is a routine internal handoff within the same organization. ai
maintainer-change maintainer-added AI (maintainer-change): eashaw is a well-established Sails Company account; addition is consistent with legitimate internal maintainer management. ai

Versions (showing 17 of 17)

Version Deps Published
2.0.7 5 / 2
2.0.6 5 / 2
2.0.5 5 / 2
2.0.4 5 / 2
2.0.3 5 / 2
2.0.2 5 / 2
2.0.1 5 / 2
2.0.0 5 / 2
1.3.0 5 / 4
1.2.3 5 / 4
1.2.2 5 / 4
1.1.1 5 / 4
1.0.3 5 / 4
1.0.2 3 / 1
1.0.1 3 / 1
1.0.0 3 / 1
0.2.0 2 / 1

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

2 findings
HIGH Publisher changed: rachaelshaw → eashaw (on 2021-03-26) provenance

This version was published by a different npm account than previous versions on 2021-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mikermcneil → rachaelshaw (on 2019-05-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-10. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: sgress454 → mikermcneil (on 2019-01-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-31. This could indicate a legitimate maintainer transition or an account compromise.

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mikermcneil → sgress454 (on 2017-03-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-10. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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