riakpbc — Greenflagged

RiakPBC is a low-level Riak protocol buffer client.

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

nlftroynisaacson

Keywords

riakpbcprotobuf

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Publisher change from nisaacson to nlf occurred in January 2014 — over 10 years ago. nlf is a well-established publisher with 84 packages and strong approval history. Not an active hijack.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): nlf was added as maintainer in 2014; this is a long-settled legitimate transfer, not a recent suspicious addition.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): nisaacson removal is part of the same decade-old legitimate transfer to nlf. No ongoing risk.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from nlf to nisaacson occurred in Dec 2013 (~10 years ago). nisaacson has 59 approved packages and a long track record. This is a historical, legitimate maintainer transition.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package dates from 2013; Sigstore provenance attestation was not available then. Expected for packages of this age.	ai	2026/04/24

Versions (showing 51 of 54)

View all versions

Version	Deps	Published
2.1.0	4 / 3	2014-10-28
2.0.3	4 / 3	2014-10-07
2.0.2	4 / 3	2014-10-03
2.0.1	4 / 3	2014-09-22
2.0.0	4 / 3	2014-09-18
1.4.2	2 / 7	2014-07-09
1.4.1	2 / 7	2014-06-18
1.4.0	2 / 7	2014-05-06
1.3.1	2 / 7	2014-04-02
1.3.0	2 / 7	2014-04-01
1.2.7	2 / 9	2014-03-25
1.2.6	2 / 9	2014-03-17
1.2.5	2 / 9	2014-02-15
1.2.4	2 / 9	2014-02-07
1.2.3	2 / 9	2014-02-03
1.2.1	2 / 9	2014-01-29
1.2.0	2 / 9	2014-01-22
1.1.5	4 / 9	2014-01-17
1.1.4	4 / 9	2014-01-15
1.1.3	4 / 9	2014-01-13
1.1.2	4 / 9	2014-01-13
1.1.1	4 / 9	2014-01-13
1.1.0	4 / 9	2014-01-13
1.0.10	3 / 9	2014-01-12
1.0.9	3 / 9	2013-12-17
1.0.8	3 / 9	2013-12-14
1.0.7	3 / 9	2013-12-13
1.0.6	3 / 8	2013-12-10
1.0.4	3 / 8	2013-12-05
1.0.3	3 / 5	2013-12-05
1.0.2	3 / 3	2013-12-05
1.0.1	3 / 3	2013-12-05
1.0.0	3 / 3	2013-12-05
0.1.4	2 / 2	2013-12-04
0.1.3	2 / 2	2013-12-04
0.1.2	2 / 2	2013-12-04
0.1.1	2 / 2	2013-12-04
0.1.0	2 / 2	2013-10-18
0.0.17	2 / 2	2013-08-09
0.0.16	2 / 2	2013-08-09
0.0.15	2 / 2	2013-08-08
0.0.14	2 / 2	2013-08-07
0.0.13	2 / 1	2013-08-06
0.0.12	2 / 1	2013-04-25
0.0.11	2 / 1	2013-04-25
0.0.10	2 / 1	2013-04-10
0.0.9	2 / 1	2013-04-09
0.0.8	2 / 1	2013-03-26
0.0.7	2 / 1	2013-03-12
0.0.6	2 / 1	2013-02-05
0.0.5	2 / 1	2013-02-04

v2.1.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.4.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.

v1.4.1

1 finding

INFO No provenance attestation provenance

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

v1.4.0

1 finding

INFO No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

INFO No provenance attestation provenance

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

v1.2.7

1 finding

INFO No provenance attestation provenance

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

v1.2.6

1 finding

INFO No provenance attestation provenance

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

v1.2.5

1 finding

INFO No provenance attestation provenance

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

v1.2.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.

v1.2.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.

v1.2.1

1 finding

INFO No provenance attestation provenance

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

v1.2.0

1 finding

INFO No provenance attestation provenance

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

v1.1.5

1 finding

INFO No provenance attestation provenance

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

v1.1.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.

v1.1.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.

v1.1.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (nisaacson) were replaced by new maintainers (nlf). This is a strong signal of a potential package hijack and requires careful review.

INFO No provenance attestation provenance

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

INFO Publisher changed: nisaacson → nlf (on 2014-01-13) provenance

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

v1.1.1

1 finding

INFO No provenance attestation provenance

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

v1.1.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nlf → nisaacson (on 2014-01-13) provenance

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

v1.0.10

1 finding

INFO No provenance attestation provenance

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

v1.0.9

1 finding

INFO No provenance attestation provenance

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

v1.0.8

1 finding

INFO No provenance attestation provenance

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

v1.0.7

1 finding

INFO No provenance attestation provenance

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

v1.0.6

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nisaacson → nlf (on 2013-12-10) provenance

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

v1.0.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.

v1.0.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.

v1.0.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.

v1.0.1

1 finding

INFO No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: nlf → nisaacson (on 2013-12-05) provenance

This version was published by a different npm account than previous versions on 2013-12-05. 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.