← Home

@sideway/address

npm Repository Homepage
7
Versions
—
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

hueniverse

Keywords

emaildomainaddressvalidation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): hueniverse and marsup are both accounts associated with the hapi.js ecosystem founder (Eran Hammer). This is a known account migration, not a hostile takeover. ai
maintainer-change maintainer-added AI (maintainer-change): marsup is the well-established primary maintainer of the hapi/sideway ecosystem; this addition reflects a legitimate account transition. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by publish under marsup is consistent with the known hapi ecosystem account migration, not an account takeover. ai

Versions (showing 7 of 7)

Version Deps Published
5.0.0 1 / 9
4.1.5 1 / 3
4.1.4 1 / 3
4.1.3 1 / 3
4.1.2 1 / 3
4.1.1 1 / 3
4.1.0 1 / 3

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

v4.1.5

2 findings
HIGH Publisher changed: hueniverse → marsup (on 2024-01-29) provenance

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

v4.1.4

1 finding
LOW No provenance attestation provenance

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

v4.1.3

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

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

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