bufrw — Greenflagged

Buffer Reading and Writing

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

usiarheikenns29shengsemrahszacklkuber-osporussfrankjcorbinkriskowalraynosabq

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within Uber org from jcorbin to russfrank in 2016; russfrank has extensive approved track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): russfrank added as maintainer in 2016 as part of normal Uber org maintenance; well-established publisher.	ai	2026/04/24

Versions (showing 33 of 33)

Version	Deps	Published
1.4.0	4 / 9	2023-10-26
1.3.0	4 / 9	2019-08-25
1.2.1	3 / 9	2016-03-23
1.2.0	3 / 9	2016-01-29
1.1.0	3 / 9	2016-01-21
1.0.1	3 / 9	2016-01-21
1.0.0	3 / 9	2016-01-21
0.9.27	3 / 9	2015-12-11
0.9.26	3 / 9	2015-11-10
0.9.25	5 / 9	2015-08-26
0.9.24	5 / 9	2015-05-20
0.9.21	5 / 8	2015-05-06
0.9.20	5 / 8	2015-04-14
0.9.19	5 / 8	2015-04-13
0.9.18	5 / 8	2015-04-13
0.9.17	5 / 8	2015-04-12
0.9.16	5 / 8	2015-04-09
0.9.15	4 / 8	2015-04-07
0.9.14	4 / 8	2015-04-07
0.9.13	4 / 8	2015-04-06
0.9.12	4 / 8	2015-04-06
0.9.11	4 / 8	2015-04-06
0.9.10	4 / 8	2015-04-04
0.9.9	4 / 8	2015-03-29
0.9.8	4 / 8	2015-03-28
0.9.7	3 / 8	2015-03-24
0.9.6	3 / 8	2015-03-24
0.9.5	1 / 10	2015-03-17
0.9.4	1 / 10	2015-03-17
0.9.3	1 / 10	2015-03-16
0.9.2	1 / 10	2015-03-15
0.9.1	1 / 10	2015-03-11
0.9.0	1 / 10	2015-03-11

v1.4.0

2 findings

HIGH Publisher changed: kriskowal → usiarhei (on 2023-10-26) provenance

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

v1.3.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: russfrank → kriskowal (on 2019-08-25) provenance

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

v1.2.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kriskowal.

LOW No provenance attestation provenance

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

INFO Publisher changed: russfrank → kriskowal (on 2016-03-23) provenance

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

v1.2.0

2 findings

HIGH Publisher changed: jcorbin → russfrank (on 2016-01-29) provenance

This version was published by a different npm account than previous versions on 2016-01-29. 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.

v1.1.0

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.

v0.9.27

1 finding

LOW No provenance attestation provenance

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

v0.9.26

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: abq → jcorbin (on 2015-11-10) provenance

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

v0.9.25

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: abq → jcorbin (on 2015-08-26) provenance

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

v0.9.24

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: jcorbin → abq (on 2015-05-20) provenance

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

v0.9.21

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: jcorbin → raynos (on 2015-05-06) provenance

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

v0.9.20

1 finding

LOW No provenance attestation provenance

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

v0.9.19

1 finding

LOW No provenance attestation provenance

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

v0.9.18

1 finding

LOW No provenance attestation provenance

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

v0.9.17

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: kriskowal → jcorbin (on 2015-04-12) provenance

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

v0.9.16

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: kriskowal → jcorbin (on 2015-04-09) provenance

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

v0.9.15

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kriskowal.

LOW No provenance attestation provenance

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

v0.9.14

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kriskowal.

LOW No provenance attestation provenance

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

INFO Publisher changed: jcorbin → kriskowal (on 2015-04-07) provenance

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

v0.9.13

1 finding

LOW No provenance attestation provenance

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

v0.9.12

1 finding

LOW No provenance attestation provenance

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

v0.9.11

1 finding

LOW No provenance attestation provenance

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

v0.9.10

1 finding

LOW No provenance attestation provenance

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

v0.9.9

1 finding

LOW No provenance attestation provenance

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

v0.9.8

1 finding

LOW No provenance attestation provenance

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

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.4

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.