@webex/common-evented
Class property decorator the adds change events to properties
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Webex SDK monorepo does not publish Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 1 / 13 | |
| 3.11.0 | 1 / 13 | |
| 3.10.0 | 1 / 13 | |
| 3.9.0 | 1 / 13 | |
| 3.8.1 | 1 / 13 | |
| 3.8.0 | 1 / 13 | |
| 3.7.0 | 1 / 13 | |
| 3.6.0 | 1 / 13 | |
| 3.5.0 | 1 / 13 | |
| 3.4.0 | 1 / 13 | |
| 3.3.1 | 1 / 13 | |
| 3.3.0 | 1 / 13 | |
| 3.2.0 | 1 / 13 | |
| 3.1.0 | 1 / 13 | |
| 3.0.0 | 1 / 13 |
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.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.
v3.1.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.
v3.0.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.