eslint-config-cityssm
ESLint rules used in the City of Sault Ste. Marie's TypeScript projects.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with consistent identity; dormancy likely reflects development cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:@eslint-community/eslint-plugin-eslint-comments | AI (phantom-deps): ESLint config re-exports plugins; not directly imported but referenced in config objects. | ai | |
| phantom-deps | phantom-dep:baseline-browser-mapping | AI (phantom-deps): Referenced in config files for browser baseline data; expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 132 versions; lack of provenance is consistent across all prior releases. | ai | |
| npm-metadata | url-dep:eslint-plugin-woke | AI (npm-metadata): GitHub URL points to the same cityssm org; intentional first-party dependency pattern stable across versions. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-promise | AI (phantom-deps): Same as eslint-plugin-n; config-only reference pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-n | AI (phantom-deps): ESLint config packages reference plugins in config objects, not via import statements; phantom-dep is a false positive here. | ai | |
| dependencies | unvetted-dep:eslint-plugin-woke | AI (dependencies): Same-org GitHub dep from cityssm; stable pattern for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 40.1.0 | 26 / 3 | |
| 40.0.1 | 26 / 3 | |
| 40.0.0 | 26 / 3 | |
| 38.2.2 | 26 / 2 | |
| 38.2.1 | 26 / 2 | |
| 37.1.0 | 26 / 2 | |
| 35.0.0 | 25 / 2 |
v40.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v40.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v40.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v38.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v38.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v37.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v35.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.