@statoscope/stats-extension-compressed
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 | missing-githead | AI (provenance): Metadata gap only, no diff vs prior approved version; publisher has long clean track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate monorepo sub-package; sparse README and no keywords are typical for internal extension packages. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating common provenance adoption; no other risk signals. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.28.1 | 4 / 0 | |
| 5.28.0 | 2 / 2 | |
| 5.25.0 | 2 / 2 | |
| 5.24.0 | 2 / 2 | |
| 5.23.0 | 2 / 2 | |
| 5.22.0 | 2 / 2 | |
| 5.19.0 | 2 / 2 | |
| 5.14.1 | 2 / 2 | |
| 5.9.0 | 2 / 2 | |
| 5.7.1 | 2 / 2 | |
| 5.7.0 | 2 / 2 | |
| 5.6.1 | 2 / 2 | |
| 5.6.0 | 2 / 2 | |
| 5.5.1 | 2 / 2 | |
| 5.4.0 | 2 / 2 | |
| 5.3.1 | 2 / 2 | |
| 5.3.0 | 2 / 2 |
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smelukov.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.