← Home

@solvapay/next

npm Repository Homepage

Next.js-specific utilities and helpers for SolvaPay SDK.

10
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

tommy-solvapay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped @solvapay/next is a Next.js SDK integration, not a nuxt typosquat. ai
typosquat typosquat.levenshtein:jest AI (typosquat): 2-edit distance false positive; package is a payment SDK, not related to jest. ai
typosquat typosquat.levenshtein:knex AI (typosquat): 2-edit distance false positive; unrelated to knex. ai
phantom-deps phantom-dep:@solvapay/core AI (phantom-deps): Same-org monorepo dep; may be re-exported transitively rather than directly imported. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.13 3 / 5
1.0.12 3 / 5
1.0.11 3 / 5
1.0.10 3 / 5
1.0.7 3 / 5
1.0.6 3 / 5
1.0.5 3 / 5
1.0.4 3 / 5
1.0.3 3 / 5
1.0.2 3 / 5

v1.0.13

1 finding
LOW No provenance attestation provenance

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

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

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

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.