← Home

@apify/markdown

npm Repository Homepage

Tools and constants shared across Apify projects.

70
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mtrunkatjancurnpetrpatekmnmkngjaroslavhejlekdrobnikjmetalwarrior665fnesvedab4nanjanbucharapify-service-account

Keywords

apify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:match-all AI (dependencies): match-all is a stable, minimal regex utility; no known advisories and consistent use across Apify packages. ai

Versions (showing 70 of 70)

Version Deps Published
3.0.74 4 / 0
3.0.73 4 / 0
3.0.72 4 / 0
3.0.71 4 / 0
3.0.70 4 / 0
3.0.69 4 / 0
3.0.67 4 / 0
3.0.66 4 / 0
3.0.65 4 / 0
3.0.64 4 / 0
3.0.63 4 / 0
3.0.62 4 / 0
3.0.61 4 / 0
3.0.60 4 / 0
3.0.59 4 / 0
3.0.58 4 / 0
3.0.57 4 / 0
3.0.56 4 / 0
3.0.55 4 / 0
3.0.53 4 / 0
3.0.51 4 / 0
3.0.50 4 / 0
3.0.49 4 / 0
3.0.48 4 / 0
3.0.47 4 / 0
3.0.46 4 / 0
3.0.45 4 / 0
3.0.44 4 / 0
3.0.43 4 / 0
3.0.42 4 / 0
3.0.41 4 / 0
3.0.40 4 / 0
3.0.39 4 / 0
3.0.38 4 / 0
3.0.35 4 / 0
3.0.34 4 / 0
3.0.33 4 / 0
3.0.32 4 / 0
3.0.31 4 / 0
3.0.30 4 / 0
3.0.29 4 / 0
3.0.28 4 / 0
3.0.27 4 / 0
3.0.26 4 / 0
3.0.25 4 / 0
3.0.24 4 / 0
3.0.23 4 / 0
3.0.22 4 / 0
3.0.21 4 / 0
3.0.20 4 / 0
3.0.19 4 / 0
3.0.18 4 / 0
3.0.17 4 / 0
3.0.16 4 / 0
3.0.15 4 / 0
3.0.14 4 / 0
3.0.13 4 / 0
3.0.12 4 / 0
3.0.11 4 / 0
3.0.10 4 / 0
3.0.9 4 / 0
3.0.8 4 / 0
3.0.7 4 / 0
3.0.6 4 / 0
3.0.5 4 / 0
3.0.4 4 / 0
3.0.3 4 / 0
3.0.2 4 / 0
3.0.1 4 / 0
3.0.0 4 / 0

v3.0.74

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.73

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.72

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.