← Home

class-utils

npm Repository Homepage

Utils for working with JavaScript classes and prototype methods.

14
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

doowbjonschlinkert

Keywords

arrayassignclasscopyctordefinedelegatedescriptorextendextendsinheritinheritancemergemethodobjectproppropertiespropertyprototypeutilutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from doowb to jonschlinkert in 2016 is a documented legitimate transition; package.json, repo, and author all consistently reference jonschlinkert. Stable for this package. ai

Versions (showing 14 of 14)

Version Deps Published
0.3.6 4 / 8
0.3.5 5 / 8
0.3.4 5 / 8
0.3.3 4 / 8
0.3.2 3 / 8
0.3.1 3 / 7
0.3.0 3 / 7
0.2.3 3 / 7
0.2.2 3 / 7
0.2.1 3 / 7
0.2.0 2 / 7
0.1.2 2 / 7
0.1.1 2 / 7
0.1.0 2 / 7

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

2 findings
HIGH Publisher changed: doowb → jonschlinkert (on 2016-03-09) provenance

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

v0.3.1

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2016-01-27) provenance

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

v0.3.0

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2015-12-01) provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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