@wix/activity-counters
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK module; templated name, no description, and no repo URL are expected patterns for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; stable false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.0.92 | 1 / 2 | |
| 1.0.91 | 1 / 2 | |
| 1.0.90 | 1 / 2 | |
| 1.0.89 | 1 / 2 | |
| 1.0.88 | 1 / 2 | |
| 1.0.87 | 1 / 2 | |
| 1.0.86 | 1 / 2 | |
| 1.0.85 | 1 / 2 | |
| 1.0.84 | 1 / 2 | |
| 1.0.83 | 1 / 2 | |
| 1.0.82 | 1 / 2 | |
| 1.0.81 | 1 / 2 | |
| 1.0.79 | 1 / 2 | |
| 1.0.78 | 1 / 2 | |
| 1.0.77 | 1 / 2 | |
| 1.0.76 | 1 / 2 | |
| 1.0.75 | 1 / 1 | |
| 1.0.74 | 1 / 1 | |
| 1.0.73 | 1 / 1 | |
| 1.0.72 | 1 / 1 | |
| 1.0.71 | 1 / 1 | |
| 1.0.70 | 1 / 1 | |
| 1.0.69 | 1 / 1 | |
| 1.0.68 | 1 / 1 | |
| 1.0.67 | 1 / 1 | |
| 1.0.66 | 1 / 1 | |
| 1.0.65 | 1 / 1 | |
| 1.0.64 | 1 / 1 | |
| 1.0.63 | 1 / 1 | |
| 1.0.62 | 1 / 1 | |
| 1.0.61 | 1 / 1 | |
| 1.0.60 | 1 / 1 | |
| 1.0.59 | 1 / 1 | |
| 1.0.58 | 1 / 1 | |
| 1.0.57 | 1 / 1 | |
| 1.0.56 | 1 / 4 | |
| 1.0.55 | 1 / 4 | |
| 1.0.54 | 1 / 4 | |
| 1.0.53 | 1 / 4 | |
| 1.0.52 | 1 / 4 | |
| 1.0.51 | 1 / 4 | |
| 1.0.50 | 1 / 4 |
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.