@haklex/rich-plugin-link-edit
Link editing 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
Versions (showing 51 of 145)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 0 / 13 | |
| 0.18.0 | 0 / 13 | |
| 0.17.1 | 0 / 13 | |
| 0.16.1 | 0 / 13 | |
| 0.16.0 | 0 / 13 | |
| 0.15.9 | 0 / 13 | |
| 0.15.7 | 0 / 13 | |
| 0.15.6 | 0 / 13 | |
| 0.15.5 | 0 / 13 | |
| 0.15.4 | 0 / 13 | |
| 0.15.2 | 0 / 13 | |
| 0.15.1 | 0 / 13 | |
| 0.15.0 | 0 / 13 | |
| 0.14.1 | 0 / 13 | |
| 0.14.0 | 0 / 13 | |
| 0.13.0 | 0 / 13 | |
| 0.12.0 | 0 / 13 | |
| 0.11.0 | 0 / 13 | |
| 0.10.0 | 0 / 13 | |
| 0.9.3 | 0 / 13 | |
| 0.9.2 | 0 / 13 | |
| 0.9.1 | 0 / 13 | |
| 0.9.0 | 0 / 13 | |
| 0.8.0 | 0 / 13 | |
| 0.7.0 | 0 / 13 | |
| 0.6.2 | 0 / 13 | |
| 0.6.1 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.0 | 0 / 13 | |
| 0.4.1 | 0 / 13 | |
| 0.4.0 | 0 / 13 | |
| 0.3.4 | 0 / 13 | |
| 0.3.3 | 0 / 13 | |
| 0.3.2 | 0 / 13 | |
| 0.3.1 | 0 / 13 | |
| 0.3.0 | 2 / 13 | |
| 0.2.0 | 2 / 13 | |
| 0.1.1 | 2 / 13 | |
| 0.1.0 | 2 / 13 | |
| 0.0.110 | 2 / 13 | |
| 0.0.109 | 2 / 13 | |
| 0.0.108 | 2 / 13 | |
| 0.0.107 | 2 / 13 | |
| 0.0.106 | 2 / 13 | |
| 0.0.105 | 2 / 13 | |
| 0.0.104 | 2 / 13 | |
| 0.0.103 | 2 / 13 | |
| 0.0.102 | 2 / 13 | |
| 0.0.101 | 2 / 13 | |
| 0.0.100 | 2 / 13 | |
| 0.0.99 | 2 / 13 |
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.