@teemill/shipping
OpenAPI client for @teemill/shipping
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 1 / 2 | |
| 0.17.0 | 1 / 2 | |
| 0.16.0 | 1 / 2 | |
| 0.15.1 | 1 / 2 | |
| 0.15.0 | 1 / 2 | |
| 0.14.0 | 1 / 2 | |
| 0.13.0 | 1 / 2 | |
| 0.12.0 | 1 / 2 | |
| 0.11.0 | 1 / 2 | |
| 0.10.5 | 1 / 2 | |
| 0.10.3 | 1 / 2 | |
| 0.10.1 | 1 / 2 | |
| 0.10.0 | 1 / 2 | |
| 0.9.3 | 1 / 2 | |
| 0.9.2 | 1 / 2 | |
| 0.9.1 | 1 / 2 | |
| 0.9.0 | 1 / 2 | |
| 0.8.2 | 1 / 2 | |
| 0.8.1 | 1 / 2 | |
| 0.8.0 | 1 / 2 | |
| 0.7.0 | 1 / 2 | |
| 0.6.2 | 0 / 1 |
v0.18.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 (js-wheeler) than the most recent previously approved version (devanjs) on 2026-07-23, but js-wheeler 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.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.