← Home

address

npm Repository Homepage

Get current machine IP, MAC and DNS servers.

16
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

fengmk2

Keywords

addressipipv4mac

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/commonjs/address.js AI (source-diff): Standard TypeScript compiler (tsc/tshy) output for CJS target; readable code, not obfuscated. Stable for this package. ai
source-diff obfuscated-file:dist/esm/address.js AI (source-diff): Standard TypeScript compiler (tsc/tshy) output for ESM target; readable code, not obfuscated. Stable for this package. ai
source-diff source-size-tripled AI (source-diff): Size increase from TypeScript rewrite with dual CJS/ESM dist outputs plus src/ included. Expected for tshy-based packages. ai

Versions (showing 16 of 16)

Version Deps Published
2.0.3 0 / 13
2.0.2 0 / 12
2.0.1 0 / 12
1.2.2 0 / 8
1.2.1 0 / 7
1.2.0 0 / 12
1.1.2 0 / 12
1.1.1 0 / 9
1.1.0 0 / 9
1.0.3 0 / 10
1.0.2 0 / 10
1.0.1 0 / 7
1.0.0 0 / 6
0.0.3 0 / 8
0.0.2 0 / 8
0.0.1 0 / 8

v2.0.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.1

3 findings
HIGH New obfuscated file: dist/commonjs/address.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/address.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

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

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