@crawlee/templates
Templates for the crawlee projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Used in build/validate scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Used in build/validate scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:yargonaut | AI (phantom-deps): Used in build/validate scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ansi-colors | AI (phantom-deps): Used in build/validate scripts; stable false positive for this package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 5 / 0 | |
| 3.16.0 | 5 / 0 | |
| 3.15.3 | 5 / 0 | |
| 3.15.2 | 5 / 0 | |
| 3.15.1 | 5 / 0 | |
| 3.15.0 | 5 / 0 | |
| 3.14.1 | 5 / 0 | |
| 3.14.0 | 5 / 0 | |
| 3.13.10 | 5 / 0 | |
| 3.13.9 | 5 / 0 | |
| 3.13.8 | 5 / 0 | |
| 3.13.7 | 5 / 0 | |
| 3.13.6 | 5 / 0 | |
| 3.13.5 | 5 / 0 | |
| 3.13.4 | 5 / 0 | |
| 3.13.3 | 5 / 0 | |
| 3.13.2 | 5 / 0 | |
| 3.13.1 | 5 / 0 | |
| 3.13.0 | 5 / 0 | |
| 3.12.2 | 5 / 0 | |
| 3.12.1 | 5 / 0 | |
| 3.12.0 | 5 / 0 | |
| 3.11.5 | 5 / 0 | |
| 3.11.4 | 5 / 0 | |
| 3.11.3 | 5 / 0 | |
| 3.11.2 | 5 / 0 | |
| 3.11.1 | 5 / 0 | |
| 3.11.0 | 5 / 0 | |
| 3.10.5 | 5 / 0 | |
| 3.10.4 | 5 / 0 | |
| 3.10.3 | 5 / 0 | |
| 3.10.2 | 5 / 0 | |
| 3.10.1 | 5 / 0 | |
| 3.10.0 | 5 / 0 |
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.