← Home

@ninetailed/experience.js-plugin-google-analytics

Ninetailed SDK plugin for Google Analytics

51
Versions
MIT
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

braunreusebastian_ninetailedfrancoiscontentful

Keywords

google-analyticsninetailedpersonalizationa/b testing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI/CD publisher is confirmed by SLSA provenance attestation; stable pattern for this org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD migration with SLSA attestation; 389 versions and org repo confirm legitimacy. ai
provenance slsa-provenance AI (provenance): Package publishes via GitHub Actions with SLSA provenance; this is the expected CI/CD pattern for this org. ai
phantom-deps phantom-dep:@ninetailed/experience.js AI (phantom-deps): Same-org monorepo dependency; declared as a peer/transitive dep, not a direct import. Stable false positive. ai

Versions (showing 51 of 59)

View all versions
Version Deps Published
7.24.2 3 / 0
7.24.0 3 / 0
7.23.2 3 / 0
7.23.1 3 / 0
7.23.0 3 / 0
7.22.0 3 / 0
7.21.3 3 / 0
7.21.2 3 / 0
7.21.1 3 / 0
7.21.0 3 / 0
7.20.6 3 / 0
7.20.5 3 / 0
7.20.4 3 / 0
7.20.3 3 / 0
7.20.2 3 / 0
7.20.1 3 / 0
7.20.0 3 / 0
7.19.0 3 / 0
7.18.13 3 / 0
7.18.11 3 / 0
7.18.10 3 / 0
7.18.9 3 / 0
7.18.8 3 / 0
7.18.7 3 / 0
7.18.6 3 / 0
7.18.5 3 / 0
7.18.4 3 / 0
7.18.3 3 / 0
7.18.2 3 / 0
7.18.1 3 / 0
7.18.0 3 / 0
7.17.6 3 / 0
7.17.5 3 / 0
7.17.4 3 / 0
7.17.2 3 / 0
7.17.1 3 / 0
7.17.0 3 / 0
7.16.0 3 / 0
7.15.1 3 / 0
7.15.0 3 / 0
7.14.2 3 / 0
7.14.0 3 / 0
7.13.0 3 / 0
7.12.1 3 / 0
7.12.0 3 / 0
7.11.1 3 / 0
7.11.0 3 / 0
7.10.0 3 / 0
7.9.3 3 / 0
7.9.2 3 / 0
7.9.1 3 / 0

v7.24.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.

v7.12.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.

v7.11.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.

v7.11.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.

v7.10.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: braunreu → francoiscontentful (on 2025-01-23, now via trusted publisher with provenance) provenance

This version was published by a different npm account (francoiscontentful) than the most recent previously approved version (braunreu) on 2025-01-23, 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.

v7.9.3

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: braunreu → francoiscontentful (on 2025-01-03, now via trusted publisher with provenance) provenance

This version was published by a different npm account (francoiscontentful) than the most recent previously approved version (braunreu) on 2025-01-03, 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.

v7.9.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.

v7.9.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.