← Home

component-xor

npm Repository Homepage

tiny xor utility function

2
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

tootallnatetjholowaychukrauchgretrofoxcorehforbeslindesaykelonyemattmuelleryieldsanthonyshortjongleberryianstormtaylorcristiandouceswatinemstagasamasadjuliangrubershtylmancalvinfodominicbarnestimoxleyjonathanongqueckezzclintwoodthehydroimpulsestephenmathiesontrevorgerhardttimaschewhughsk

Keywords

xor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate 2015 transfer within the component ecosystem org; mattmueller is a well-established publisher. ai
maintainer-change maintainer-added AI (maintainer-change): Component org shared maintainer model; all added maintainers are known ecosystem contributors. ai
publish-pattern dormant-publish AI (publish-pattern): Tiny stable utility; infrequent publishes are expected. Last publish was 2015. ai
bogus-package bogus-package AI (bogus-package): amasad spam flag is a false positive; they are a known component org member. ai

Versions (showing 2 of 2)

Version Deps Published
0.0.4 0 / 2
0.0.3 0 / 2

v0.0.4

2 findings
HIGH Publisher changed: tootallnate → mattmueller (on 2015-03-31) provenance

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

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.