← Home

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

Ninetailed SDK plugin for Google Tag Manager

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-tagmanagerninetailedpersonalizationa/b testing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI is a documented, legitimate pattern; SLSA attestation corroborates integrity. ai
publish-pattern dormant-publish AI (publish-pattern): 305 versions in registry and SLSA provenance attestation indicate an active, legitimate project resuming releases via CI. ai
phantom-deps phantom-dep:@eslint/js AI (phantom-deps): ESLint framework dependency loaded by convention; stable pattern. ai
phantom-deps phantom-dep:@eslint/eslintrc AI (phantom-deps): ESLint framework dependency loaded by convention; stable pattern. ai
phantom-deps phantom-dep:jsonc-eslint-parser AI (phantom-deps): Config-file parser; referenced in ESLint config, not direct import. ai
phantom-deps phantom-dep:@ninetailed/experience.js AI (phantom-deps): Same-org peer dependency; stable monorepo pattern. ai

Versions (showing 51 of 59)

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