← Home

@wisemen/coordinates

npm Repository Homepage
32
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 missing-githead AI (provenance): gitHead absence is consistent with GitHub Actions publish flow using SLSA attestation instead. ai
provenance slsa-provenance AI (provenance): Package consistently publishes with SLSA provenance via GitHub Actions. ai
provenance publisher-changed AI (provenance): New publisher is an established wisemen-org contributor with 80 approved packages; org-internal handoff. ai

Versions (showing 32 of 32)

Version Deps Published
0.1.1 2 / 7
0.1.0 2 / 7
0.0.31 2 / 7
0.0.30 2 / 7
0.0.29 2 / 7
0.0.28 2 / 5
0.0.27 2 / 5
0.0.26 2 / 5
0.0.25 2 / 5
0.0.24 2 / 5
0.0.23 2 / 5
0.0.22 2 / 5
0.0.21 2 / 5
0.0.20 1 / 3
0.0.19 0 / 3
0.0.18 0 / 3
0.0.17 0 / 3
0.0.16 0 / 3
0.0.15 0 / 3
0.0.14 0 / 3
0.0.13 0 / 3
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 3 / 3
0.0.4 3 / 3
0.0.3 3 / 4
0.0.2 3 / 4

v0.0.3

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