@wisemen/vue-core-query
Supply chain provenance
Status for the latest visible version.
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
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 | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org library; sparse metadata is typical for private/internal packages published publicly. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same org pattern; missing description is consistent across @wisemen scoped packages. | ai | |
| 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 | |
| phantom-deps | phantom-dep:@wisemen/vue-core-components | AI (phantom-deps): Same-org dependency; likely used in type declarations or re-exports. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.0.47 | 2 / 20 | |
| 0.0.46 | 2 / 20 | |
| 0.0.45 | 2 / 20 | |
| 0.0.44 | 2 / 20 | |
| 0.0.43 | 2 / 20 | |
| 0.0.42 | 2 / 20 | |
| 0.0.41 | 2 / 20 | |
| 0.0.40 | 2 / 20 | |
| 0.0.39 | 2 / 20 | |
| 0.0.38 | 2 / 20 | |
| 0.0.37 | 2 / 20 | |
| 0.0.36 | 1 / 21 | |
| 0.0.35 | 1 / 21 | |
| 0.0.34 | 1 / 20 | |
| 0.0.33 | 1 / 20 | |
| 0.0.32 | 1 / 18 | |
| 0.0.31 | 1 / 18 | |
| 0.0.3 | 1 / 18 | |
| 0.0.2 | 1 / 18 | |
| 0.0.1 | 1 / 18 |
v0.0.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fullmetaljs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fullmetaljs) than the most recent previously approved version (wouter.appwise) on 2025-03-27, but fullmetaljs 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.33
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fullmetaljs) than the most recent previously approved version (wouter.appwise) on 2025-03-07, but fullmetaljs 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.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wouter.appwise) than the most recent previously approved version (robbe95) on 2024-07-03, but wouter.appwise 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.