← Home

@learncard/helpers

Shared helpers for LearnCard packages

65
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

gerardoparcustard7smurflo2taylorbeestonjonny2lips

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is documented CI/CD automation, backed by SLSA provenance attestation. ai
phantom-deps phantom-dep:query-string AI (phantom-deps): Monorepo build artifact; declared dep used in config/build context, stable false positive. ai
phantom-deps phantom-dep:@learncard/types AI (phantom-deps): Same-org type dependency; expected phantom in monorepo type-only usage. ai

Versions (showing 65 of 65)

Version Deps Published
1.3.10 7 / 12
1.3.9 7 / 12
1.3.8 7 / 12
1.3.7 7 / 12
1.3.6 7 / 12
1.3.5 7 / 12
1.3.4 7 / 12
1.3.3 5 / 12
1.3.2 5 / 12
1.3.1 5 / 12
1.3.0 5 / 12
1.2.17 5 / 12
1.2.16 5 / 12
1.2.14 5 / 12
1.2.13 5 / 12
1.2.12 5 / 12
1.2.11 5 / 12
1.2.10 5 / 12
1.2.9 5 / 12
1.2.8 5 / 12
1.2.7 5 / 12
1.2.6 5 / 12
1.2.4 5 / 12
1.2.2 5 / 12
1.2.1 5 / 12
1.1.32 2 / 11
1.1.31 2 / 11
1.1.30 2 / 11
1.1.29 2 / 11
1.1.28 2 / 11
1.1.27 2 / 11
1.1.26 2 / 11
1.1.25 2 / 11
1.1.24 2 / 11
1.1.23 2 / 11
1.1.21 2 / 11
1.1.20 2 / 11
1.1.19 2 / 11
1.1.18 2 / 11
1.1.17 2 / 11
1.1.16 2 / 11
1.1.15 2 / 11
1.1.14 2 / 11
1.1.13 2 / 11
1.1.12 2 / 11
1.1.11 2 / 11
1.1.10 2 / 11
1.1.9 2 / 11
1.1.8 2 / 11
1.1.7 2 / 11
1.1.6 2 / 11
1.1.5 2 / 11
1.1.4 2 / 11
1.1.3 2 / 11
1.1.2 2 / 11
1.1.1 2 / 11
1.1.0 2 / 11
1.0.20 1 / 11
1.0.19 1 / 11
1.0.18 1 / 11
1.0.17 1 / 11
1.0.16 1 / 11
1.0.15 1 / 11
1.0.14 1 / 11
1.0.13 1 / 11

v1.3.10

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.

v1.3.9

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.

v1.3.8

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.

v1.3.7

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.

v1.3.6

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.

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.20

1 finding
LOW No provenance attestation provenance

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

v1.0.19

1 finding
LOW No provenance attestation provenance

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

v1.0.18

1 finding
LOW No provenance attestation provenance

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

v1.0.17

1 finding
LOW No provenance attestation provenance

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

v1.0.16

1 finding
LOW No provenance attestation provenance

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

v1.0.15

1 finding
LOW No provenance attestation provenance

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

v1.0.14

1 finding
LOW No provenance attestation provenance

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

v1.0.13

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.