@statoscope/report-writer
Statoscope report writer
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): pako is a well-known compression lib, benign addition explaining size growth. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase attributable to bundling pako, not injected payload. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript type definitions loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:@types/pako | AI (phantom-deps): TypeScript type definitions loaded by convention, not direct imports. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.28.1 | 4 / 0 | |
| 5.27.0 | 3 / 1 | |
| 5.25.1 | 3 / 1 | |
| 5.25.0 | 3 / 1 | |
| 5.22.0 | 1 / 1 | |
| 5.20.0 | 1 / 1 | |
| 5.14.1 | 1 / 1 | |
| 5.9.0 | 1 / 1 | |
| 5.8.0 | 1 / 1 | |
| 5.7.1 | 1 / 1 | |
| 5.7.0 | 1 / 1 | |
| 5.5.1 | 1 / 1 | |
| 5.5.0 | 1 / 1 | |
| 5.4.2 | 1 / 1 | |
| 5.3.2 | 1 / 1 | |
| 5.3.1 | 1 / 1 | |
| 5.3.0 | 1 / 1 | |
| 5.2.0 | 1 / 1 | |
| 5.1.0 | 1 / 1 | |
| 5.0.0 | 1 / 0 |
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.