@tmlmobilidade/repo-version
A CLI tool to bump the version of a NodeJS package.
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 |
|---|---|---|---|---|
| license | copyleft-license:AGPL-3.0-or-later | AI (license): Package is intentionally AGPL-3.0; stable license choice for this org's tooling. | ai | |
| provenance | publisher-changed-known-maintainer | AI (provenance): Known maintainer rotation within the same org; stable pattern for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): 246 versions in registry indicates automated versioning pipeline; rapid publishes are expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 232 versions from this publisher; not a security concern for this package. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 20260212.1701.52 | 1 / 3 | |
| 20260212.1101.35 | 1 / 3 | |
| 20260212.51.30 | 1 / 3 | |
| 20260209.2202.10 | 1 / 3 | |
| 20260209.1731.14 | 1 / 3 | |
| 20260208.2343.21 | 1 / 3 | |
| 20260208.202.17 | 1 / 3 | |
| 20260206.1935.37 | 1 / 3 | |
| 20260206.1919.21 | 1 / 3 | |
| 20260204.911.28 | 1 / 3 | |
| 20260203.1404.18 | 1 / 3 | |
| 20260203.1129.22 | 1 / 3 | |
| 20260203.1103.48 | 1 / 3 | |
| 20260201.1250.27 | 1 / 3 | |
| 20260201.1210.10 | 1 / 3 | |
| 20260130.1504.40 | 1 / 3 | |
| 20260130.1448.58 | 1 / 3 | |
| 20260130.1025.54 | 1 / 3 | |
| 20260129.1456.48 | 1 / 3 | |
| 20260129.1254.47 | 1 / 3 | |
| 20260128.2320.18 | 1 / 3 | |
| 20260128.2225.6 | 1 / 3 | |
| 20260126.1852.36 | 1 / 3 | |
| 20260121.2332.4 | 1 / 3 | |
| 20260121.2317.48 | 1 / 3 | |
| 20260121.1805.44 | 1 / 3 | |
| 20260113.1437.46 | 1 / 3 | |
| 20260110.331.6 | 1 / 3 | |
| 20260110.323.39 | 1 / 3 | |
| 20260107.1017.45 | 1 / 3 | |
| 20260105.1950.4 | 1 / 3 | |
| 20260103.2047.14 | 1 / 3 | |
| 20251229.1636.59 | 1 / 3 | |
| 20251229.1447.48 | 1 / 3 |
v20260212.1701.52
1 findingPackage 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.
v20260212.51.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260209.2202.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260209.1731.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260208.2343.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260208.202.17
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.
v20260206.1919.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260204.911.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260203.1404.18
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260203.1103.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260201.1250.27
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.
v20260130.1504.40
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.1025.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260129.1456.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260129.1254.47
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.
v20260128.2225.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260126.1852.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260121.2332.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260121.2317.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260121.1805.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260113.1437.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260110.331.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260110.323.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260107.1017.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260105.1950.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260103.2047.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20251229.1636.59
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.