← Home

@siteimprove/alfa-future

npm Repository Homepage
35
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

ahinpmsi-npm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@siteimprove/alfa-array AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-monad AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-thunk AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-mapper AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-functor AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-callback AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-iterable AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-thenable AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-applicative AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai
dependencies unvetted-dep:@siteimprove/alfa-continuation AI (dependencies): Sibling package in the same Siteimprove alfa monorepo; same trusted publisher. ai

Versions (showing 35 of 35)

Version Deps Published
0.117.0 10 / 1
0.116.0 10 / 1
0.115.1 10 / 1
0.114.3 10 / 1
0.114.1 10 / 1
0.114.0 10 / 1
0.107.0 10 / 1
0.106.1 10 / 1
0.104.1 10 / 1
0.104.0 10 / 1
0.103.3 10 / 1
0.103.2 10 / 1
0.103.1 10 / 1
0.103.0 10 / 1
0.102.0 10 / 1
0.101.0 10 / 1
0.100.1 10 / 1
0.100.0 10 / 1
0.99.0 10 / 1
0.98.0 10 / 1
0.97.0 10 / 1
0.96.0 10 / 1
0.95.0 10 / 1
0.94.1 10 / 1
0.94.0 10 / 1
0.93.8 10 / 1
0.93.7 10 / 1
0.93.6 10 / 1
0.93.2 10 / 1
0.93.1 10 / 1
0.92.0 10 / 1
0.91.2 10 / 1
0.91.0 10 / 1
0.90.1 10 / 1
0.89.5 10 / 1

v0.103.3

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.

v0.103.2

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.

v0.103.1

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.

v0.103.0

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.

v0.102.0

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.

v0.101.0

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.

v0.100.1

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.

v0.100.0

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.

v0.99.0

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.

v0.98.0

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.

v0.97.0

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.

v0.96.0

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.

v0.95.0

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.

v0.94.1

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.

v0.94.0

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.

v0.93.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.

v0.93.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.

v0.93.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.

v0.93.2

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.

v0.93.1

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.

v0.92.0

2 findings
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.

INFO Publisher changed: ahinpm → si-npm (on 2024-09-11, now via trusted publisher with provenance) provenance

This version was published by a different npm account (si-npm) than the most recent previously approved version (ahinpm) on 2024-09-11, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.91.2

2 findings
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.

INFO Publisher changed: ahinpm → si-npm (on 2024-09-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (si-npm) than the most recent previously approved version (ahinpm) on 2024-09-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.91.0

1 finding
LOW No provenance attestation provenance

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

v0.90.1

1 finding
LOW No provenance attestation provenance

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

v0.89.5

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.