@salesforce/o11y-reporter
21
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
ire-npm-team-userjimjagsalesforce-releasesjasonschroeder-sfdcmobifylwc-adminsalesforce-admin
Keywords
salesforceo11yreporter
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:o11y | AI (dependencies): o11y is Salesforce's own observability library; this package is explicitly a wrapper around it. Dependency is expected and legitimate for all versions of this package. | ai | |
| dependencies | unvetted-dep:o11y_schema | AI (dependencies): o11y_schema is Salesforce's own observability schema library; this package is explicitly a wrapper around it. Dependency is expected and legitimate for all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is published via GitHub Actions CI/CD under the @salesforce scope; lack of Sigstore provenance is acceptable given the automated publishing pipeline and established package history. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.8.5 | 2 / 18 | |
| 1.8.4 | 2 / 18 | |
| 1.8.3 | 2 / 18 | |
| 1.8.2 | 2 / 18 | |
| 1.8.1 | 2 / 18 | |
| 1.8.0 | 2 / 17 | |
| 1.7.4 | 2 / 17 | |
| 1.7.3 | 2 / 17 | |
| 1.7.0 | 2 / 17 | |
| 1.6.0 | 2 / 17 | |
| 1.5.0 | 2 / 17 | |
| 1.4.0 | 2 / 17 | |
| 1.3.4 | 2 / 17 | |
| 1.3.3 | 2 / 17 | |
| 1.3.2 | 2 / 17 | |
| 1.3.1 | 2 / 17 | |
| 1.3.0 | 2 / 17 | |
| 1.2.0 | 2 / 17 | |
| 1.1.2 | 2 / 17 | |
| 1.1.1 | 2 / 17 | |
| 1.1.0 | 2 / 17 |
v1.8.5
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.