@tmlmobilidade/go-types-shared
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
Keywords
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 20260612.1446.12 | 2 / 6 | |
| 20260612.1126.8 | 2 / 6 | |
| 20260612.214.31 | 2 / 6 | |
| 20260611.1804.42 | 2 / 6 | |
| 20260611.1651.27 | 2 / 6 | |
| 20260611.1647.17 | 2 / 6 | |
| 20260611.1634.38 | 2 / 6 | |
| 20260611.1546.48 | 2 / 6 | |
| 20260611.1527.25 | 2 / 6 |
v20260612.1446.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260612.1126.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260612.214.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1804.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1651.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1647.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1634.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1546.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260611.1527.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.