← Home

getcontributors

npm Repository Homepage

Fetch all the contributors from a github repository, github organisation, or github search

49
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

baluptonbevryme

Keywords

browsercontributorsesnextgithubmaintainersmodulenodeorganisationorganizationownerspackage.jsontypedtypestypescriptusers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): balupton → bevry is a legitimate organizational account transition; both are Benjamin Lupton's accounts. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): bevry is the organizational npm account for balupton/Bevry Pty Ltd; this is a legitimate account consolidation, not a hostile takeover. ai
phantom-deps phantom-dep:eslint AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:typedoc AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:prettier AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:projectz AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:valid-module AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:assert-helpers AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:kava AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. Stable false positive for this package. ai
phantom-deps phantom-dep:make-deno-edition AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:eslint-config-bevry AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:eslint-config-prettier AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:eslint-plugin-prettier AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:@typescript-eslint/parser AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:@bevry/update-contributors AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:@typescript-eslint/eslint-plugin AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:valid-directory AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai
phantom-deps phantom-dep:surge AI (phantom-deps): Dev tooling package accidentally placed in dependencies; not imported at runtime. ai

Versions (showing 49 of 49)

Version Deps Published
2.23.0 5 / 17
2.22.0 5 / 17
2.21.0 5 / 17
2.20.0 5 / 17
2.19.0 5 / 17
2.18.0 5 / 17
2.17.0 5 / 17
2.16.0 5 / 17
2.15.0 6 / 17
2.14.0 22 / 17
2.13.0 5 / 17
2.12.0 5 / 17
2.11.0 5 / 16
2.10.0 5 / 16
2.9.0 5 / 16
2.8.0 5 / 16
2.7.0 5 / 16
2.6.0 5 / 16
2.5.2 5 / 16
2.5.1 5 / 15
2.5.0 5 / 15
2.4.0 5 / 15
2.3.0 5 / 15
2.2.0 5 / 15
2.1.0 5 / 15
2.0.0 5 / 15
1.10.0 6 / 12
1.7.0 6 / 12
1.6.0 6 / 12
1.5.0 6 / 12
1.4.5 6 / 8
1.4.4 6 / 8
1.4.3 6 / 8
1.4.2 6 / 8
1.4.1 6 / 8
1.3.7 5 / 5
1.3.6 5 / 5
1.3.5 5 / 5
1.3.4 5 / 5
1.3.3 5 / 5
1.3.2 5 / 5
1.3.1 5 / 4
1.3.0 5 / 4
1.2.0 9 / 4
1.1.1 6 / 4
1.1.0 6 / 4
1.0.2 6 / 4
1.0.1 6 / 4
1.0.0 2 / 3

v2.23.0

1 finding
LOW No provenance attestation provenance

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

v2.22.0

1 finding
LOW No provenance attestation provenance

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

v2.21.0

1 finding
LOW No provenance attestation provenance

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

v2.20.0

1 finding
LOW No provenance attestation provenance

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

v2.19.0

1 finding
LOW No provenance attestation provenance

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

v2.18.0

1 finding
LOW No provenance attestation provenance

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

v2.17.0

1 finding
LOW No provenance attestation provenance

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

v2.16.0

1 finding
LOW No provenance attestation provenance

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

v2.15.0

1 finding
LOW No provenance attestation provenance

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

v2.14.0

1 finding
LOW No provenance attestation provenance

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

v2.13.0

1 finding
LOW No provenance attestation provenance

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

v2.12.0

1 finding
LOW No provenance attestation provenance

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

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.10.0

1 finding
LOW No provenance attestation provenance

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

v2.9.0

1 finding
LOW No provenance attestation provenance

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

v2.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.10.0

2 findings
HIGH Publisher changed: bevry → bevryme (on 2019-12-09) provenance

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

2 findings
HIGH Publisher changed: bevry → bevryme (on 2019-11-10) provenance

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

2 findings
HIGH Publisher changed: bevry → bevryme (on 2019-11-09) provenance

This version was published by a different npm account than previous versions on 2019-11-09. 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.5.0

2 findings
HIGH Publisher changed: bevry → bevryme (on 2019-09-10) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

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

2 findings
HIGH Publisher changed: balupton → bevry (on 2017-02-27) provenance

This version was published by a different npm account than previous versions on 2017-02-27. 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.4.1

2 findings
HIGH Publisher changed: balupton → bevry (on 2017-02-24) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.3.6

1 finding
LOW No provenance attestation provenance

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

v1.3.5

1 finding
LOW No provenance attestation provenance

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

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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

v1.2.0

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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.