@simplysm/lint
심플리즘 패키지 - ESLint plugin
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stylelint-config-standard | AI (phantom-deps): Config-only dep; referenced in stylelint config files, not imported directly — stable pattern. | ai | |
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): Lint config package; stylelint deps are referenced in config files, not imported directly — stable pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-no-unresolved-module | AI (phantom-deps): Config-only dep; referenced in stylelint config files, not imported directly — stable pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-config-tailwindcss | AI (phantom-deps): Config-only dep; referenced in stylelint config files, not imported directly — stable pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-no-unsupported-browser-features | AI (phantom-deps): Config-only dep; referenced in stylelint config files, not imported directly — stable pattern. | ai | |
| dependencies | unvetted-dep:angular-eslint | AI (dependencies): angular-eslint is a well-known, widely-used linting package appropriate for this ESLint plugin. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo with 146 versions; automated rapid publishes are the established pattern for this publisher. | ai | |
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): Scoped package @simplysm/lint is a legitimate ESLint plugin, not a typosquat of eslint. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): eslint-import-resolver-typescript is used as a resolver in ESLint config, not directly imported. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a peer/config dependency referenced in config files, not directly imported in source. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): No relation to pino; levenshtein match is coincidental for this ESLint plugin package. | ai |
Versions (showing 75 of 182)
| Version | Deps | Published |
|---|---|---|
| 13.0.90 | 10 / 2 | |
| 13.0.89 | 10 / 2 | |
| 13.0.88 | 10 / 2 | |
| 13.0.87 | 10 / 2 | |
| 13.0.86 | 10 / 2 | |
| 13.0.85 | 10 / 2 | |
| 13.0.84 | 10 / 2 | |
| 13.0.83 | 10 / 2 | |
| 13.0.82 | 10 / 2 | |
| 13.0.81 | 10 / 2 | |
| 13.0.80 | 10 / 2 | |
| 13.0.78 | 10 / 2 | |
| 13.0.77 | 10 / 2 | |
| 13.0.76 | 10 / 2 | |
| 13.0.74 | 15 / 2 | |
| 13.0.72 | 15 / 2 | |
| 13.0.71 | 15 / 2 | |
| 13.0.70 | 15 / 2 | |
| 13.0.69 | 15 / 2 | |
| 13.0.68 | 15 / 2 | |
| 13.0.67 | 15 / 2 | |
| 13.0.66 | 15 / 2 | |
| 13.0.65 | 15 / 2 | |
| 13.0.64 | 14 / 2 | |
| 13.0.62 | 14 / 2 | |
| 13.0.61 | 14 / 2 | |
| 13.0.60 | 14 / 2 | |
| 13.0.59 | 14 / 2 | |
| 13.0.58 | 14 / 2 | |
| 13.0.57 | 14 / 2 | |
| 13.0.56 | 14 / 2 | |
| 13.0.55 | 14 / 2 | |
| 13.0.53 | 14 / 2 | |
| 13.0.51 | 14 / 2 | |
| 13.0.50 | 14 / 2 | |
| 13.0.49 | 14 / 2 | |
| 13.0.48 | 14 / 2 | |
| 13.0.47 | 14 / 2 | |
| 13.0.45 | 14 / 2 | |
| 13.0.44 | 14 / 2 | |
| 13.0.43 | 14 / 2 | |
| 13.0.42 | 14 / 2 | |
| 13.0.41 | 14 / 2 | |
| 13.0.40 | 14 / 2 | |
| 13.0.39 | 14 / 2 | |
| 13.0.38 | 14 / 2 | |
| 13.0.37 | 14 / 2 | |
| 13.0.36 | 14 / 2 | |
| 13.0.35 | 14 / 2 | |
| 13.0.34 | 14 / 2 | |
| 13.0.33 | 14 / 2 | |
| 13.0.32 | 14 / 2 | |
| 13.0.31 | 14 / 2 | |
| 13.0.30 | 14 / 2 | |
| 13.0.29 | 14 / 2 | |
| 13.0.28 | 14 / 2 | |
| 13.0.27 | 14 / 2 | |
| 13.0.26 | 14 / 2 | |
| 13.0.25 | 14 / 2 | |
| 13.0.24 | 14 / 2 | |
| 13.0.23 | 14 / 2 | |
| 13.0.22 | 14 / 2 | |
| 13.0.20 | 14 / 2 | |
| 13.0.18 | 14 / 2 | |
| 13.0.16 | 14 / 2 | |
| 13.0.15 | 14 / 2 | |
| 13.0.14 | 14 / 2 | |
| 13.0.13 | 14 / 2 | |
| 13.0.12 | 14 / 2 | |
| 13.0.11 | 14 / 2 | |
| 13.0.10 | 14 / 2 | |
| 13.0.8 | 14 / 2 | |
| 13.0.7 | 14 / 2 | |
| 13.0.3 | 14 / 2 | |
| 13.0.2 | 14 / 2 |
v13.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.