@tmlmobilidade/go-types-apex
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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 20260617.1318.33 | 2 / 5 | |
| 20260616.2252.19 | 2 / 5 | |
| 20260616.2238.2 | 2 / 5 | |
| 20260616.1147.27 | 2 / 5 | |
| 20260616.229.43 | 2 / 5 | |
| 20260616.222.7 | 2 / 5 | |
| 20260616.214.2 | 2 / 5 | |
| 20260616.54.25 | 2 / 5 | |
| 20260615.2224.24 | 2 / 5 | |
| 20260615.1640.33 | 2 / 5 | |
| 20260615.1553.39 | 2 / 5 | |
| 20260615.1437.21 | 2 / 5 | |
| 20260615.1034.33 | 2 / 5 | |
| 20260615.1002.3 | 2 / 5 | |
| 20260615.953.39 | 2 / 5 | |
| 20260615.923.29 | 2 / 5 | |
| 20260612.1446.12 | 2 / 5 | |
| 20260612.1126.8 | 2 / 5 | |
| 20260612.214.31 | 2 / 5 | |
| 20260611.1804.42 | 2 / 5 | |
| 20260611.1651.27 | 2 / 5 | |
| 20260611.1647.17 | 2 / 5 | |
| 20260611.1634.38 | 2 / 5 | |
| 20260611.1546.48 | 2 / 5 | |
| 20260611.1527.25 | 2 / 5 |
v20260617.1318.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.2252.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.2238.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.1147.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.229.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.222.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.214.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260616.54.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.2224.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.1640.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.1553.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.1437.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260615.1034.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.1002.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.953.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260615.923.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260611.1546.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260611.1527.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.