← Home

ipv4

npm Repository Homepage

ipv4

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

brunoyangxudafengziczhu

Keywords

ipipv4

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change (brunoyang → xudafeng) occurred in 2017; repo URL matches xudafeng's GitHub org, indicating a legitimate ownership transfer. xudafeng has 68 approved packages and 0 rejected. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): chalk is a well-known terminal styling library; appropriate for a CLI tool. Phantom dep finding is a false positive for this package. ai
phantom-deps phantom-dep:copy-paste AI (phantom-deps): copy-paste is a well-known clipboard utility; appropriate for a CLI tool. Phantom dep finding is a false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
1.0.4 3 / 4
1.0.2 3 / 2
1.0.1 2 / 1
1.0.0 0 / 1
0.0.5 0 / 1
0.0.4 0 / 1
0.0.3 1 / 1
0.0.2 1 / 1
0.0.1 0 / 1

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: brunoyang → xudafeng (on 2017-07-03) provenance

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

2 findings
HIGH Publisher changed: brunoyang → xudafeng (on 2016-12-14) provenance

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

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: xudafeng → brunoyang (on 2016-09-21) provenance

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

v0.0.4

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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