← Home

@wisemen/pagination

npm Repository Homepage
16
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

wouter.appwisekobe-kwanten-wisemenjorenvandeweyerrobbe95fullmetaljsmaartensijmkenswisemen-sysopspeethadaanpersoonsjonasvannieuwenhuijsenyuhanghujonasbeckerssebastiaanvanspauwenjeroen-vc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from named maintainer to GitHub Actions CI is documented by SLSA provenance; consistent with org-level automation. ai
provenance missing-githead AI (provenance): Missing gitHead is a side-effect of the CI/CD publish pipeline change; SLSA provenance provides stronger commit linkage. ai
npm-metadata no-description AI (npm-metadata): Scoped org package; missing description is a style issue, not a malice indicator for this publisher. ai

Versions (showing 16 of 16)

Version Deps Published
1.0.0 1 / 5
0.1.1 1 / 5
0.1.0 1 / 5
0.0.13 1 / 5
0.0.12 0 / 3
0.0.11 0 / 3
0.0.10 0 / 3
0.0.9 0 / 3
0.0.8 0 / 3
0.0.7 0 / 3
0.0.6 0 / 3
0.0.5 0 / 4
0.0.4 0 / 4
0.0.3 0 / 4
0.0.2 0 / 4
0.0.1 0 / 3

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: kobe-kwanten-wisemen → jorenvandeweyer (on 2025-04-11, known maintainer) provenance

This version was published by a different npm account (jorenvandeweyer) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-04-11, but jorenvandeweyer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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

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: jorenvandeweyer → kobe-kwanten-wisemen (on 2025-03-13, known maintainer) provenance

This version was published by a different npm account (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-03-13, but kobe-kwanten-wisemen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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.