← Home

@tmlmobilidade/import-gtfs

npm Repository Homepage
100
Versions
AGPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

joaovasconcelosjusimen

Keywords

public transittmltransportes metropolitanos de lisboaservices

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New deps are all same-org @tmlmobilidade scoped packages; not a third-party supply chain risk. ai
dependencies unvetted-dep:@tmlmobilidade/dates AI (dependencies): Same-org internal dependency; consistent with all other @tmlmobilidade/* deps in this package. ai
dependencies unvetted-dep:@tmlmobilidade/connectors AI (dependencies): Sibling package within the same @tmlmobilidade org; consistent with the rest of the ecosystem. ai
publish-pattern rapid-publish AI (publish-pattern): Package has 277 versions with frequent automated CI publishes; rapid publish is normal for this org. ai
phantom-deps phantom-dep:@tmlmobilidade/strings AI (phantom-deps): Same org scope; likely used transitively or via re-export pattern, stable false positive. ai
phantom-deps phantom-dep:@tmlmobilidade/interfaces AI (phantom-deps): Same org scope; type-only import pattern common in TypeScript packages, stable false positive. ai
provenance no-provenance AI (provenance): Org does not use Sigstore provenance; consistent across all 269 versions. ai
npm-metadata no-description AI (npm-metadata): Internal org tooling package; missing description is consistent across the org's packages. ai
dependencies unvetted-dep:@tmlmobilidade/sqlite AI (dependencies): Internal sibling dep from same org; consistent pattern across all @tmlmobilidade packages. ai
dependencies unvetted-dep:@tmlmobilidade/interfaces AI (dependencies): Internal sibling dep from same org; consistent pattern across all @tmlmobilidade packages. ai
dependencies unvetted-dep:@tmlmobilidade/logger AI (dependencies): Internal sibling dep from same org; consistent pattern across all @tmlmobilidade packages. ai

Versions (showing 100 of 104)

Version Deps Published
20260607.1410.59 8 / 6
20260607.1318.3 8 / 6
20260604.2309.43 8 / 6
20260604.9.7 8 / 6
20260602.1654.41 8 / 6
20260602.1156.15 8 / 6
20260601.1839.20 8 / 6
20260601.1808.3 8 / 6
20260601.1657.26 8 / 6
20260601.1041.27 8 / 6
20260531.1600.32 8 / 6
20260528.1652.52 8 / 6
20260528.1142.29 8 / 6
20260527.1804.46 8 / 6
20260526.1648.32 8 / 6
20260525.1830.15 8 / 6
20260525.1751.19 8 / 6
20260525.1717.19 8 / 6
20260525.1615.59 8 / 6
20260525.1608.2 8 / 6
20260525.1333.38 8 / 6
20260519.2010.45 6 / 6
20260519.1741.30 6 / 6
20260519.1152.59 6 / 6
20260518.1511.41 6 / 6
20260518.1500.45 6 / 6
20260518.901.35 6 / 6
20260518.827.12 6 / 6
20260517.2113.47 6 / 6
20260517.2052.46 6 / 6
20260515.1629.19 6 / 6
20260515.1056.47 6 / 6
20260514.1444.18 6 / 6
20260513.1602.22 6 / 6
20260513.1532.47 6 / 6
20260513.1439.37 6 / 6
20260513.1432.15 6 / 6
20260511.1451.46 6 / 6
20260509.331.19 6 / 6
20260507.2220.24 6 / 6
20260506.4.20 6 / 6
20260505.2319.13 6 / 6
20260505.2312.1 6 / 6
20260505.1315.54 6 / 6
20260504.1731.48 6 / 6
20260504.1617.17 6 / 6
20260504.1404.49 6 / 6
20260504.1142.3 6 / 6
20260504.1112.57 6 / 6
20260502.1945.53 6 / 6
20260429.1713.40 6 / 6
20260424.1050.20 6 / 6
20260420.1828.16 6 / 6
20260420.1455.19 6 / 6
20260418.1237.24 6 / 6
20260408.1128.43 6 / 6
20260406.1442.3 6 / 6
20260406.1418.25 6 / 6
20260331.1620.53 6 / 6
20260327.0.15 6 / 6
20260326.1518.29 6 / 6
20260324.1249.38 6 / 6
20260322.1829.11 6 / 6
20260322.1655.45 6 / 6
20260316.1355.29 6 / 6
20260309.2221.31 6 / 6
20260305.1852.13 6 / 6
20260305.1602.46 6 / 6
20260302.1453.8 6 / 6
20260226.1857.59 6 / 6
20260225.1317.2 6 / 6
20260225.1312.4 6 / 6
20260223.1747.6 6 / 6
20260222.2150.54 6 / 6
20260222.2136.56 6 / 6
20260222.1530.55 6 / 6
20260217.1056.55 6 / 6
20260217.1056.18 6 / 6
20260217.220.4 6 / 6
20260216.1613.20 6 / 6
20260212.1701.51 6 / 6
20260212.1101.35 6 / 6
20260208.202.18 6 / 6
20260204.911.28 6 / 6
20260201.1250.27 6 / 6
20260201.1128.44 6 / 6
20260130.1504.39 6 / 6
20260130.1104.56 6 / 6
20260128.2357.59 6 / 6
20260128.2248.28 6 / 6
20260121.1805.44 6 / 6
20260113.1457.7 6 / 6
20260107.1017.44 6 / 6
20260103.2047.14 6 / 6
20251229.932.45 6 / 6
20251222.1756.6 6 / 6
20251222.1552.52 6 / 6
20251217.1540.37 6 / 6
20251211.1230.30 6 / 6
20251206.1045.7 6 / 6
Showing 100 of 104 Next page →

v20260607.1410.59

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260607.1318.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260604.2309.43

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260604.9.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260602.1654.41

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260602.1156.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260601.1839.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260601.1808.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260601.1657.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260601.1041.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260531.1600.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260528.1652.52

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jusimen → joaovasconcelos (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-28, 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.

v20260528.1142.29

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jusimen → joaovasconcelos (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-28, 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.

v20260527.1804.46

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jusimen → joaovasconcelos (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (joaovasconcelos) than the most recent previously approved version (jusimen) on 2026-05-27, 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.

v20260526.1648.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1830.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1751.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1717.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1615.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1608.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1333.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260519.2010.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260519.1741.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260519.1152.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.1511.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.1500.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.901.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.827.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260517.2113.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260517.2052.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260515.1629.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260515.1056.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260514.1444.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260513.1602.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260513.1532.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260513.1439.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260513.1432.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260511.1451.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260509.331.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260507.2220.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260506.4.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260505.2319.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260505.2312.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260505.1315.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1731.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1617.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1404.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1142.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1112.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260502.1945.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260429.1713.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260424.1050.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260420.1828.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260420.1455.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260418.1237.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260408.1128.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260406.1442.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260406.1418.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260331.1620.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260327.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260326.1518.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260324.1249.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260322.1829.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260322.1655.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260316.1355.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260309.2221.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260305.1852.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260305.1602.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260302.1453.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260226.1857.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260225.1317.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260225.1312.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260223.1747.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260222.2150.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260222.2136.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260222.1530.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260217.1056.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260217.1056.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260217.220.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260216.1613.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260212.1701.51

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260212.1101.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260208.202.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260204.911.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260201.1250.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260201.1128.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260130.1504.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260130.1104.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260128.2357.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260128.2248.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260121.1805.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260113.1457.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260107.1017.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260103.2047.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251229.932.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251222.1756.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251222.1552.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251217.1540.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251211.1230.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20251206.1045.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.