@tmlmobilidade/utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency automated CI/CD publishing is the established pattern for this package (1098 versions). | ai | |
| dependencies | unvetted-dep:@tmlmobilidade/dates | AI (dependencies): First-party sibling package from the same org; consistent with the rest of the @tmlmobilidade/* dependency pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are zod, luxon, and same-org @tmlmobilidade/* packages — all benign in context of this publisher. | ai | |
| provenance | no-provenance | AI (provenance): This org consistently publishes without Sigstore provenance; stable pattern across 1081 versions. | ai |
Versions (showing 40 of 143)
| Version | Deps | Published |
|---|---|---|
| 20260203.1103.48 | 3 / 5 | |
| 20260201.1250.27 | 3 / 5 | |
| 20260201.1210.11 | 3 / 5 | |
| 20260201.1128.44 | 3 / 5 | |
| 20260130.1504.39 | 3 / 5 | |
| 20260130.1448.57 | 3 / 5 | |
| 20260130.1104.56 | 3 / 5 | |
| 20260130.1025.54 | 3 / 5 | |
| 20260130.130.49 | 3 / 5 | |
| 20260129.1456.48 | 3 / 5 | |
| 20260129.1254.47 | 3 / 5 | |
| 20260128.2357.59 | 3 / 5 | |
| 20260128.2320.17 | 3 / 5 | |
| 20260128.2248.28 | 3 / 5 | |
| 20260126.1852.36 | 3 / 5 | |
| 20260121.2332.6 | 3 / 5 | |
| 20260121.2317.50 | 3 / 5 | |
| 20260121.1805.44 | 3 / 5 | |
| 20260113.1457.7 | 3 / 5 | |
| 20260113.1437.46 | 3 / 5 | |
| 20260110.331.4 | 3 / 5 | |
| 20260107.1017.44 | 3 / 5 | |
| 20260105.1950.3 | 3 / 5 | |
| 20260103.2056.41 | 3 / 5 | |
| 20260103.2047.14 | 3 / 5 | |
| 20251229.932.45 | 3 / 5 | |
| 20251222.1756.6 | 3 / 5 | |
| 20251222.1647.5 | 3 / 5 | |
| 20251222.1552.52 | 3 / 5 | |
| 20251222.1537.24 | 3 / 5 | |
| 20251218.110.37 | 3 / 5 | |
| 20251217.1540.37 | 3 / 5 | |
| 20251212.1456.57 | 3 / 5 | |
| 20251211.1246.9 | 3 / 5 | |
| 20251211.1230.30 | 3 / 5 | |
| 20251206.1045.7 | 3 / 5 | |
| 20251205.1154.10 | 3 / 5 | |
| 20251204.1130.15 | 3 / 5 | |
| 20251202.1821.43 | 3 / 5 | |
| 20251202.1817.5 | 3 / 5 |
v20260203.1103.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260201.1250.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260201.1210.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260201.1128.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260130.1504.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260130.1448.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260130.1104.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260130.1025.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260130.130.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260129.1456.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260129.1254.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260128.2357.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260128.2320.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260128.2248.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260126.1852.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260121.2332.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260121.2317.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260121.1805.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260113.1457.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260113.1437.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260110.331.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260107.1017.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260105.1950.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260103.2056.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260103.2047.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251229.932.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251222.1756.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251222.1647.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251222.1552.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251222.1537.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251218.110.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251217.1540.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251212.1456.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251211.1246.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251211.1230.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251206.1045.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251205.1154.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251204.1130.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251202.1821.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251202.1817.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.