@sasjs/lint
1
Versions
—
License
Yes
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
krishna-acondyallanboweyury_shkoda
Keywords
sasSASjsviyalintformatting
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): Scoped @sasjs/lint is a legitimate SAS linter; Levenshtein match to eslint is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @sasjs/lint is a legitimate SAS linter; Levenshtein match to pino is coincidental. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): preinstall runs node checkNodeVersion — a local version check, stable pattern for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.4.3 | 2 / 5 |
v2.4.3
2 findings
HIGH
Package has 'preinstall' script
install-scripts
Script: node checkNodeVersion
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.