@wisemen/vue-core-query No license 11 versions

@wisemen/vue-core-query

npm

11

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

wouter.appwisekobe-kwanten-wisemenjorenvandeweyerrobbe95fullmetaljsmaartensijmkenswisemen-sysopspeethadaanpersoonsjonasvannieuwenhuijsenyuhanghujonasbeckerssebastiaanvanspauwen

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): No provenance is common; no other risk signals elevate this.	ai	2026/05/20
bogus-package	bogus-package	AI (bogus-package): Internal scoped org library; sparse metadata is typical for private/internal packages published publicly.	ai	2026/05/20
npm-metadata	no-description	AI (npm-metadata): Same org pattern; missing description is consistent across @wisemen scoped packages.	ai	2026/05/20
phantom-deps	phantom-dep:@tanstack/vue-query	AI (phantom-deps): Re-exported peer dep; may be used in type declarations or config rather than direct imports.	ai	2026/05/20
phantom-deps	phantom-dep:@wisemen/vue-core-components	AI (phantom-deps): Same-org dependency; likely used in type declarations or re-exports.	ai	2026/05/20

Versions (showing 11 of 11)

Version	Deps	Published
0.0.47	2 / 20	2025-09-16
0.0.46	2 / 20	2025-09-10
0.0.45	2 / 20	2025-08-25
0.0.44	2 / 20	2025-08-25
0.0.43	2 / 20	2025-08-07
0.0.42	2 / 20	2025-08-06
0.0.41	2 / 20	2025-07-28
0.0.40	2 / 20	2025-07-11
0.0.39	2 / 20	2025-07-08
0.0.38	2 / 20	2025-06-26
0.0.37	2 / 20	2025-05-28

v0.0.47

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

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

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

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

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

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

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

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

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

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

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.