@penclipai/adapter-qwen-local
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 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2026.606.0 | 2 / 2 | |
| 2026.605.0 | 2 / 2 | |
| 2026.602.3 | 2 / 2 | |
| 2026.602.2 | 2 / 2 | |
| 2026.602.1 | 2 / 2 | |
| 2026.602.0 | 2 / 2 | |
| 2026.531.0 | 2 / 2 | |
| 2026.530.0 | 2 / 2 | |
| 2026.522.0 | 2 / 2 | |
| 2026.521.0 | 2 / 2 | |
| 2026.519.0 | 2 / 2 | |
| 2026.514.0 | 2 / 2 | |
| 2026.512.0 | 2 / 2 | |
| 2026.511.1 | 2 / 2 | |
| 2026.511.0 | 2 / 2 | |
| 2026.508.2 | 2 / 2 | |
| 2026.508.1 | 2 / 2 | |
| 2026.508.0 | 2 / 2 | |
| 2026.507.0 | 2 / 2 | |
| 2026.506.0 | 2 / 2 | |
| 2026.505.0 | 2 / 2 | |
| 2026.426.0 | 2 / 2 | |
| 2026.424.0 | 2 / 2 | |
| 2026.419.0 | 2 / 2 | |
| 2026.414.2 | 2 / 2 | |
| 2026.414.1 | 2 / 2 | |
| 2026.414.0 | 2 / 2 | |
| 2026.413.0 | 2 / 2 | |
| 2026.412.0 | 2 / 2 | |
| 2026.411.0 | 2 / 2 | |
| 2026.410.0 | 2 / 2 | |
| 2026.406.0 | 2 / 2 | |
| 2026.404.0 | 2 / 2 |
v2026.606.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.605.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.602.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.602.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.602.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.602.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.531.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.530.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.522.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.521.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.519.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.514.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.512.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.511.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.511.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.508.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.508.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.508.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.507.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.506.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.505.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.426.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.424.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.419.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.414.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.414.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.