@tinkoff/request-url-utils
Support library for @tinkoff/request
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
Keywords
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 2 / 0 | |
| 0.10.2 | 2 / 0 | |
| 0.10.1 | 2 / 0 | |
| 0.10.0 | 2 / 0 | |
| 0.9.3 | 2 / 0 | |
| 0.9.2 | 2 / 0 | |
| 0.9.1 | 2 / 0 |
v0.10.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 (super_oleg) than the most recent previously approved version (marsibarsi) on 2023-12-06, but super_oleg 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.9.3
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 (marsibarsi) than the most recent previously approved version (meskill) on 2023-08-02, but marsibarsi 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.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.