@qrvey/utils
Helper, Utils for all Qrvey Projects
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): xss, tslib, @stencil/store are all established, well-known packages with no malicious history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Qrvey org team rotation; new maintainers are within the same organization. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Qrvey org team rotation; removal consistent with internal team changes. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.18.0 | 6 / 26 | |
| 1.17.1 | 6 / 26 | |
| 1.17.0 | 6 / 26 | |
| 1.12.23 | 3 / 16 |
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jose.gonzalez.qrvey) than the most recent previously approved version (mario.vasco) on 2026-05-30, but jose.gonzalez.qrvey 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.
v1.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jose.gonzalez.qrvey) than the most recent previously approved version (mario.vasco) on 2026-05-07, but jose.gonzalez.qrvey 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.
v1.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.