← Home

class-is

npm Repository Homepage

Enhances a JavaScript class by adding an is<Class> property to compare types between realms.

9
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

acostalimaafonsovreisandregoncalvesdevandrenevescapelofilipediasffsdiogohugomrdiasivolimasilvajonnybelmarcooliveiramoxyhqnlfonsecapaulobmarcospedromiguelssricardo-silva91ruimonteiroruipnevessatazorvascosantos

Keywords

withiswith-isisclassis-classsymbolsrealmsinstanceofinstance-of

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): fsdiogo (Diogo Silva) is the listed author in package.json and part of the moxystudio org that owns the repo. Transition from satazor is a legitimate org-internal handoff. ai
source-diff source-size-tripled AI (source-diff): Zero runtime deps; size increase from v1.0.0 to v1.1.0 attributable to added tooling configs and tests, not injected payloads. No install scripts or suspicious files added. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.0 0 / 8
1.0.0 0 / 8
0.5.1 0 / 8
0.5.0 0 / 8
0.4.0 0 / 8
0.3.1 0 / 10
0.3.0 0 / 10
0.2.1 0 / 10
0.2.0 0 / 10

v1.1.0

2 findings
HIGH Publisher changed: satazor → fsdiogo (on 2018-04-04) provenance

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

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: fsdiogo → satazor (on 2018-03-30) provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

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