← Home

@be-link/ecommerce-user-service-node-sdk

npm
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

8848top-devhanguodongwangml0310

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:tsoa AI (dependencies): tsoa is a well-established TypeScript REST/OpenAPI framework; its use here is consistent with the package's swagger/build scripts. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is tsoa, a legitimate build/codegen tool; not a suspicious or novel package. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Private RFC-1918 IP (192.168.56.220) used as internal NAT host; not a public exfiltration endpoint. ai
phantom-deps phantom-dep:safe-stable-stringify AI (phantom-deps): safe-stable-stringify is declared in package.json dependencies; phantom-dep heuristic false positive. ai

Versions (showing 12 of 12)

Version Deps Published
0.1.122 7 / 0
0.1.107 7 / 0
0.1.81 7 / 0
0.1.47 6 / 0
0.0.20 5 / 0
0.0.7 5 / 0
0.0.6 4 / 1
0.0.5 4 / 1
0.0.4 4 / 1
0.0.3 4 / 1
0.0.2 4 / 1
0.0.1 4 / 1

v0.1.122

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

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

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.