← Home

@particle-network/auth

npm
10
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

pantaovayparticle-web3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex encoding used for crypto address/hash utilities, not payload obfuscation. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 used for transaction signing data, standard wallet SDK behavior. ai
bogus-package bogus-package AI (bogus-package): Sparse metadata typical of scoped SDK sub-packages; downloads/age confirm legitimacy. ai
npm-metadata no-description AI (npm-metadata): Missing description only, no behavioral signal. ai
dependencies unvetted-dep:@particle-network/analytics AI (dependencies): First-party sibling package in same scoped namespace. ai

Versions (showing 10 of 10)

Version Deps Published
1.3.1 5 / 4
1.3.0 5 / 4
1.2.2 5 / 4
1.2.1 5 / 4
1.2.0 5 / 4
1.1.1 5 / 4
1.1.0 5 / 4
1.0.2 5 / 4
1.0.1 5 / 4
1.0.0 5 / 4

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

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

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

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

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

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

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