← Home

ip6addr

npm Repository Homepage
8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

todd.whitemankusorwyattmichael.hicksbahamatchudleytchameroydbuellpfmooneymelloc

Keywords

ipipv4ipv6cidrsubnet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): Long-stable publisher change within Joyent org, no takeover pattern. ai
maintainer-change maintainer-added AI (maintainer-change): Joyent org maintainer list churn, stable over years. ai
publish-pattern new-deps-added AI (publish-pattern): jsprim is a well-known, benign dependency. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.5 2 / 2
0.2.4 2 / 2
0.2.3 2 / 2
0.2.2 1 / 2
0.2.1 2 / 2
0.2.0 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2

v0.2.5

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.

v0.2.4

2 findings
MEDIUM Publisher changed: melloc → bahamat (on 2021-11-03, unremoved on npm for 1720d) provenance

This version was published by a different npm account (bahamat) than the most recent previously approved version (melloc) on 2021-11-03. It has since remained available on npm for 1720 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

2 findings
MEDIUM Publisher changed: pfmooney → melloc (on 2016-10-06, unremoved on npm for 3574d) provenance

This version was published by a different npm account (melloc) than the most recent previously approved version (pfmooney) on 2016-10-06. It has since remained available on npm for 3574 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.2.1

2 findings
MEDIUM Publisher changed: pfmooney → melloc (on 2016-08-05, unremoved on npm for 3636d) provenance

This version was published by a different npm account (melloc) than the most recent previously approved version (pfmooney) on 2016-08-05. It has since remained available on npm for 3636 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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