@axinom/mosaic-id-utils
Shared types used by id-service for integration clients
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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 1 / 4 | |
| 0.27.0 | 1 / 4 | |
| 0.26.0 | 1 / 4 | |
| 0.25.0 | 1 / 4 | |
| 0.24.0 | 1 / 3 | |
| 0.23.4 | 1 / 3 | |
| 0.23.3 | 1 / 3 | |
| 0.23.2 | 1 / 3 | |
| 0.23.1 | 1 / 3 | |
| 0.23.0 | 1 / 3 | |
| 0.22.0 | 1 / 3 | |
| 0.21.0 | 1 / 3 | |
| 0.20.0 | 1 / 3 | |
| 0.19.0 | 1 / 3 | |
| 0.18.0 | 1 / 3 | |
| 0.17.0 | 1 / 3 | |
| 0.16.0 | 1 / 3 | |
| 0.15.19 | 1 / 3 | |
| 0.15.18 | 1 / 3 | |
| 0.15.17 | 1 / 3 |
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.