@tmlmobilidade/controllers
These are shared controllers to retrieve and prepare common data across apps.
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): Package uses date-based automated versioning with 215 published versions; rapid publishes are the normal release pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is from the same @tmlmobilidade org; consistent with internal package expansion pattern across 198 versions. | ai | |
| dependencies | unvetted-dep:@tmlmobilidade/interfaces | AI (dependencies): Sibling package from same org/monorepo; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/websocket | AI (phantom-deps): @fastify/websocket is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Org consistently publishes without provenance; stable pattern across 189 versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 20260602.2322.45 | 6 / 7 | |
| 20260525.1830.15 | 6 / 7 | |
| 20260519.2046.53 | 6 / 7 | |
| 20260519.1741.30 | 6 / 7 | |
| 20260429.1713.40 | 5 / 7 | |
| 20260305.1602.46 | 5 / 7 | |
| 20260226.1419.7 | 7 / 7 | |
| 20260216.2140.51 | 7 / 7 | |
| 20260212.1101.35 | 7 / 7 | |
| 20260203.1129.22 | 7 / 7 |
v20260602.2322.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260525.1830.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-25, but joaovasconcelos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v20260519.2046.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260519.1741.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260429.1713.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260305.1602.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260226.1419.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260216.2140.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260212.1101.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260203.1129.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.