@crawlee/memory-storage
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 11 / 0 | |
| 3.16.0 | 10 / 0 | |
| 3.15.3 | 10 / 0 | |
| 3.15.2 | 10 / 0 | |
| 3.15.1 | 10 / 0 | |
| 3.15.0 | 10 / 0 | |
| 3.14.1 | 10 / 0 | |
| 3.14.0 | 10 / 0 | |
| 3.13.10 | 10 / 0 | |
| 3.13.9 | 10 / 0 | |
| 3.13.8 | 10 / 0 | |
| 3.13.7 | 10 / 0 | |
| 3.13.6 | 10 / 0 | |
| 3.13.5 | 10 / 0 | |
| 3.13.4 | 10 / 0 | |
| 3.13.3 | 10 / 0 | |
| 3.13.2 | 10 / 0 | |
| 3.13.1 | 10 / 0 | |
| 3.13.0 | 10 / 0 | |
| 3.12.2 | 10 / 0 | |
| 3.12.1 | 10 / 0 | |
| 3.12.0 | 10 / 0 | |
| 3.11.5 | 10 / 0 | |
| 3.11.4 | 10 / 0 | |
| 3.11.3 | 10 / 0 | |
| 3.11.2 | 10 / 0 | |
| 3.11.1 | 10 / 0 | |
| 3.11.0 | 10 / 0 | |
| 3.10.5 | 10 / 0 | |
| 3.10.4 | 10 / 0 | |
| 3.10.3 | 10 / 0 | |
| 3.10.2 | 10 / 0 | |
| 3.10.1 | 10 / 0 | |
| 3.10.0 | 10 / 0 | |
| 3.9.2 | 10 / 0 | |
| 3.9.1 | 10 / 0 | |
| 3.9.0 | 10 / 0 | |
| 3.8.2 | 10 / 0 | |
| 3.8.1 | 10 / 0 | |
| 3.8.0 | 10 / 0 | |
| 3.7.3 | 10 / 0 | |
| 3.7.2 | 10 / 0 | |
| 3.7.1 | 10 / 0 | |
| 3.7.0 | 10 / 0 | |
| 3.6.2 | 10 / 0 | |
| 3.6.1 | 10 / 0 | |
| 3.6.0 | 10 / 0 | |
| 3.5.8 | 10 / 0 | |
| 3.5.7 | 10 / 0 | |
| 3.5.6 | 10 / 0 | |
| 3.5.5 | 10 / 0 | |
| 3.5.4 | 10 / 0 | |
| 3.5.3 | 10 / 0 | |
| 3.5.2 | 10 / 0 | |
| 3.5.1 | 10 / 0 | |
| 3.5.0 | 10 / 0 | |
| 3.4.2 | 10 / 0 | |
| 3.4.1 | 10 / 0 | |
| 3.4.0 | 10 / 0 | |
| 3.3.3 | 10 / 0 | |
| 3.3.2 | 10 / 0 | |
| 3.3.1 | 10 / 0 | |
| 3.3.0 | 10 / 0 | |
| 3.2.2 | 10 / 0 | |
| 3.2.1 | 10 / 0 | |
| 3.2.0 | 10 / 0 | |
| 3.1.2 | 10 / 0 | |
| 3.1.1 | 10 / 0 | |
| 3.1.0 | 10 / 0 | |
| 3.0.4 | 9 / 0 | |
| 3.0.3 | 9 / 0 | |
| 3.0.2 | 9 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 |
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (b4nan) than the most recent previously approved version (apify-service-account) on 2023-08-31, but b4nan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsThis version was published by a different npm account (apify-service-account) than the most recent previously approved version (b4nan) on 2023-05-31. It has since remained available on npm for 1147 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.