@tmlmobilidade/gtfs-validator
A GTFS Validator
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): Established org package with 118 versions; missing Sigstore attestation is a process gap, not a security signal. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs local dist/scripts/postinstall.js — no remote fetch, consistent with build artifact setup for this org's packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 20260506.1340.8 | 1 / 7 | |
| 20260506.1127.1 | 1 / 7 | |
| 20260505.1358.19 | 1 / 7 | |
| 20260505.1309.34 | 1 / 7 | |
| 20260504.927.37 | 1 / 7 | |
| 20260502.1936.18 | 1 / 7 | |
| 20260430.1642.6 | 1 / 7 | |
| 20260429.1502.27 | 1 / 7 | |
| 20260427.1332.34 | 1 / 7 | |
| 20260424.1518.32 | 1 / 7 | |
| 20260424.1442.39 | 1 / 7 | |
| 20260424.1152.49 | 1 / 7 | |
| 20260421.1405.11 | 1 / 7 | |
| 20260421.1254.58 | 1 / 7 | |
| 20260421.1129.12 | 1 / 7 | |
| 20260417.1638.55 | 1 / 7 | |
| 20260417.1347.9 | 1 / 7 | |
| 20260416.1131.17 | 1 / 7 | |
| 20260416.1126.11 | 1 / 7 | |
| 20260414.1445.25 | 1 / 7 | |
| 20260410.1054.36 | 1 / 7 | |
| 20251126.1641.1 | 1 / 7 |
v20260506.1340.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260506.1127.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260505.1358.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260505.1309.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260504.927.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260502.1936.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260430.1642.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260429.1502.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260424.1518.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260424.1442.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260424.1152.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260421.1405.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260421.1254.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260421.1129.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260417.1638.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260417.1347.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260416.1131.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260416.1126.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260414.1445.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20260410.1054.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251126.1641.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.