@walkeros/server-destination-tiktok
TikTok Events API server destination for walkerOS
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): Package migrated to GitHub Actions CI/CD publishing with SLSA attestation; this is the expected pattern for this org going forward. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @walkeros/* packages; monorepo publish pattern without 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 | 2 / 1 | |
| 4.0.1 | 2 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.4.2 | 2 / 1 | |
| 3.4.1 | 2 / 1 | |
| 3.4.0 | 2 / 1 | |
| 3.3.1 | 2 / 1 | |
| 3.3.0 | 2 / 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.