eslint-plugin-absolute
ESLint plugin for AbsoluteJS
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with 53 approved packages; likely CI environment change, not a supply-chain concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Niche ESLint plugin for AbsoluteJS framework; sparse README and no keywords are expected for a focused utility. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for simple property access in a type-guard helper; not obfuscation. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.11.24 | 0 / 11 | |
| 0.11.23 | 0 / 11 | |
| 0.11.22 | 0 / 11 | |
| 0.11.21 | 0 / 11 | |
| 0.11.20 | 0 / 11 | |
| 0.11.19 | 0 / 11 | |
| 0.11.18 | 0 / 11 | |
| 0.11.17 | 0 / 11 | |
| 0.11.16 | 0 / 11 | |
| 0.11.15 | 0 / 11 | |
| 0.11.14 | 0 / 11 | |
| 0.11.13 | 0 / 11 | |
| 0.11.12 | 0 / 11 | |
| 0.11.11 | 0 / 11 | |
| 0.11.10 | 0 / 11 | |
| 0.11.9 | 0 / 10 | |
| 0.11.8 | 0 / 10 | |
| 0.11.7 | 0 / 10 | |
| 0.11.6 | 0 / 10 | |
| 0.11.5 | 0 / 10 | |
| 0.11.4 | 0 / 10 | |
| 0.11.3 | 0 / 10 | |
| 0.11.2 | 0 / 10 | |
| 0.11.1 | 0 / 10 | |
| 0.11.0 | 0 / 10 | |
| 0.10.1 | 0 / 10 | |
| 0.10.0 | 0 / 10 | |
| 0.9.0 | 0 / 10 | |
| 0.8.0 | 0 / 10 | |
| 0.7.0 | 0 / 10 | |
| 0.6.0 | 0 / 10 | |
| 0.5.0 | 0 / 10 | |
| 0.4.0 | 0 / 10 | |
| 0.3.0 | 0 / 10 | |
| 0.2.8 | 0 / 10 | |
| 0.2.7 | 0 / 10 | |
| 0.2.6 | 0 / 10 | |
| 0.2.5 | 0 / 10 | |
| 0.2.4 | 0 / 10 | |
| 0.2.3 | 0 / 10 | |
| 0.2.2 | 0 / 10 | |
| 0.2.1 | 0 / 10 | |
| 0.2.0 | 0 / 9 | |
| 0.1.6 | 0 / 7 | |
| 0.1.5 | 0 / 5 | |
| 0.1.4 | 0 / 5 | |
| 0.1.3 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 5 | |
| 0.0.3 | 0 / 5 |
v0.11.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
v0.11.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexkahndev.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.