@walkeros/web-destination-linkedin
LinkedIn Insight Tag web destination for walkerOS (conversion tracking, retargeting, demographic insights)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is intentional for this monorepo; SLSA attestation confirms integrity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @walkeros/core, a first-party sibling package at matching version 4.1.0 — consistent with monorepo refactor. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by extraction of shared code into @walkeros/core; not a malicious stub replacement. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all walkerOS packages; org does not use Sigstore attestation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 2 / 1 | |
| 4.1.1 | 2 / 1 | |
| 4.1.0 | 2 / 1 | |
| 4.0.2 | 1 / 1 | |
| 4.0.1 | 1 / 1 | |
| 4.0.0 | 1 / 1 | |
| 3.4.2 | 1 / 1 | |
| 3.4.1 | 1 / 1 | |
| 3.4.0 | 1 / 1 | |
| 3.3.1 | 1 / 1 | |
| 3.3.0 | 1 / 1 |
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.