@tmlmobilidade/consts
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across all @tmlmobilidade/* packages; stable false positive for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-internal constants package; missing description is a stable pattern for this publisher. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency automated versioning pattern consistent across 230 published versions of this org package. | ai | |
| dependencies | unvetted-dep:@tmlmobilidade/dates | AI (dependencies): Same-org dependency (@tmlmobilidade); consistent with this package's established pattern of intra-org deps. | ai |
Versions (showing 25 of 127)
| Version | Deps | Published |
|---|---|---|
| 20260121.2332.6 | 0 / 6 | |
| 20260121.2317.50 | 0 / 6 | |
| 20260121.1805.44 | 0 / 6 | |
| 20260113.1457.7 | 0 / 6 | |
| 20260113.1437.46 | 0 / 6 | |
| 20260110.331.4 | 0 / 6 | |
| 20260107.1017.44 | 0 / 6 | |
| 20260105.1950.3 | 0 / 6 | |
| 20260103.2056.41 | 0 / 6 | |
| 20260103.2047.14 | 0 / 6 | |
| 20251229.932.45 | 0 / 6 | |
| 20251222.1756.6 | 0 / 6 | |
| 20251222.1647.5 | 0 / 6 | |
| 20251222.1552.52 | 0 / 6 | |
| 20251222.1537.24 | 0 / 6 | |
| 20251218.110.37 | 0 / 6 | |
| 20251217.1540.37 | 0 / 6 | |
| 20251212.1456.57 | 0 / 6 | |
| 20251211.1246.9 | 0 / 6 | |
| 20251211.1230.30 | 0 / 6 | |
| 20251206.1045.7 | 0 / 6 | |
| 20251205.1154.10 | 0 / 6 | |
| 20251204.1130.15 | 0 / 6 | |
| 20251202.1821.43 | 0 / 6 | |
| 20251202.1817.5 | 0 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v20251211.1246.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251211.1230.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251206.1045.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v20251202.1821.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20251202.1817.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.