@microsoft/eslint-plugin-sdl
ESLint plugin focused on common security issues and misconfigurations discoverable during static testing as part of Microsoft Security Development Lifecycle (SDL)
1
Versions
MIT
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
microsoft1esankatopomareztosmolkamkacmar_msft
Keywords
eslinteslintplugineslint-pluginsdl
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:eslint-plugin-security | AI (dependencies): eslint-plugin-security is a well-known, legitimate ESLint plugin and a natural dependency for an SDL-focused ESLint plugin. Not a risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require loads only the package's own package.json via a static path join. No user-controlled input; benign metadata-reading pattern stable across versions. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 3 / 6 |
v1.1.0
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.