@tmlmobilidade/backupd
A backup service for databases.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): react listed as a dependency in a backup service but not imported; likely a misconfiguration, not a security risk. | ai | |
| dependencies | unvetted-dep:@tmlmobilidade/dates | AI (dependencies): Internal org dependency from the same @tmlmobilidade scope; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@tmlmobilidade/interfaces | AI (dependencies): Internal org dependency from the same @tmlmobilidade scope; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal package with consistent publishing pattern; provenance not enabled across the monorepo. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo with 237 versions; rapid publishes are consistent with automated CI releasing sibling packages simultaneously. | ai | |
| phantom-deps | phantom-dep:@tmlmobilidade/utils | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this org's monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@types/archiver | AI (phantom-deps): Type-only package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@tmlmobilidade/consts | AI (phantom-deps): Same-org package; stable false positive for this org's monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@tmlmobilidade/types | AI (phantom-deps): Same-org package; stable false positive for this org's monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@tmlmobilidade/logger | AI (phantom-deps): Same-org package; stable false positive for this org's monorepo pattern. | ai | |
| phantom-deps | phantom-dep:resolve-tspaths | AI (phantom-deps): Build tool referenced in scripts/config, not directly imported — expected pattern. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 20260611.1655.15 | 14 / 4 | |
| 20260602.2322.53 | 14 / 4 | |
| 20260518.827.11 | 14 / 4 | |
| 20260517.1740.22 | 14 / 4 | |
| 20260504.1130.46 | 14 / 4 | |
| 20260504.1126.21 | 14 / 4 | |
| 20260504.1114.17 | 14 / 4 | |
| 20260504.1029.40 | 14 / 4 | |
| 20260504.1011.39 | 14 / 4 | |
| 20260502.1951.37 | 14 / 4 | |
| 20260429.1713.34 | 14 / 4 | |
| 20260421.1529.44 | 14 / 4 | |
| 20260421.1523.13 | 14 / 4 | |
| 20260418.1237.24 | 14 / 4 | |
| 20260407.1655.56 | 14 / 4 | |
| 20260330.1735.59 | 14 / 4 | |
| 20260304.1819.11 | 15 / 4 | |
| 20260216.2140.50 | 15 / 4 | |
| 20260206.1935.37 | 15 / 4 | |
| 20260205.2022.4 | 15 / 4 | |
| 20260201.1210.10 | 15 / 4 | |
| 20260201.1128.44 | 15 / 4 | |
| 20260130.1448.58 | 15 / 4 | |
| 20260130.1104.55 | 15 / 4 | |
| 20260128.2320.18 | 15 / 4 | |
| 20251229.1447.48 | 15 / 4 |
v20260611.1655.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260602.2322.53
2 findingsPackage 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-06-02, 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.
v20260518.827.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260517.1740.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260504.1130.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260504.1126.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260504.1114.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260504.1029.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260504.1011.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260502.1951.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260429.1713.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260421.1529.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260421.1523.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260418.1237.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260407.1655.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260330.1735.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260304.1819.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260216.2140.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260206.1935.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260205.2022.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260201.1210.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260201.1128.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260130.1448.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260130.1104.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260128.2320.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251229.1447.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.