@penclipai/adapter-cursor-cloud
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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2026.606.0 | 3 / 2 | |
| 2026.605.0 | 3 / 2 | |
| 2026.602.3 | 3 / 2 | |
| 2026.602.2 | 3 / 2 | |
| 2026.602.1 | 3 / 2 | |
| 2026.602.0 | 3 / 2 | |
| 2026.531.0 | 3 / 2 | |
| 2026.530.0 | 3 / 2 | |
| 2026.522.0 | 3 / 2 | |
| 2026.521.0 | 3 / 2 | |
| 2026.519.0 | 3 / 2 | |
| 2026.514.0 | 3 / 2 | |
| 2026.512.0 | 3 / 2 | |
| 2026.511.1 | 3 / 2 | |
| 2026.511.0 | 3 / 2 | |
| 0.3.1 | 3 / 0 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.