@tmlmobilidade/eslint
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@humanwhocodes/momoa | AI (phantom-deps): Config package; referenced in config files, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/eslint | AI (phantom-deps): Framework-scoped type package; loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): ESLint plugin package; loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Config package; postcss loaded via stylelint config convention. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Config package; typescript referenced in config files, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:stylelint-config-recess-order | AI (phantom-deps): Config package; stylelint configs referenced in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:stylelint-config-standard | AI (phantom-deps): Config package; stylelint configs referenced in config files, not code imports. | ai |
Versions (showing 25 of 268)
| Version | Deps | Published |
|---|---|---|
| 20260316.1439.45 | 14 / 5 | |
| 20260316.1355.29 | 14 / 5 | |
| 20260309.2221.31 | 14 / 5 | |
| 20260309.1855.59 | 14 / 5 | |
| 20260308.1313.9 | 14 / 5 | |
| 20260306.1635.15 | 14 / 5 | |
| 20260305.1918.43 | 14 / 5 | |
| 20260305.1852.13 | 14 / 5 | |
| 20260305.1602.46 | 14 / 5 | |
| 20260302.1453.8 | 13 / 5 | |
| 20260302.1416.42 | 13 / 5 | |
| 20260226.1857.59 | 13 / 5 | |
| 20260226.1419.7 | 13 / 5 | |
| 20260225.1759.30 | 13 / 5 | |
| 20260225.1338.31 | 13 / 5 | |
| 20260225.1317.2 | 13 / 5 | |
| 20260225.1312.4 | 13 / 5 | |
| 20260225.1134.40 | 13 / 5 | |
| 20260223.1747.6 | 13 / 5 | |
| 20260222.2150.54 | 13 / 5 | |
| 20260222.2136.56 | 19 / 6 | |
| 20260222.2116.56 | 19 / 6 | |
| 20260222.1537.50 | 19 / 6 | |
| 20260222.1530.55 | 19 / 6 | |
| 20260222.1525.56 | 19 / 6 |
v20260316.1439.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260316.1355.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260309.2221.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260309.1855.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260308.1313.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260306.1635.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260305.1918.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260305.1852.13
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260302.1453.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260302.1416.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260226.1857.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260226.1419.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260225.1759.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260225.1338.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260225.1317.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260225.1312.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260225.1134.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260223.1747.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.2150.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.2136.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.2116.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.1537.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.1530.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20260222.1525.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.