@statoscope/helpers
Statoscope utils
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): Legitimate deps (archy/jora) matching package's tree/query rendering purpose. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-running monorepo package with steady maintainer history; dormancy is a scheduling artifact, not takeover. | ai | |
| dependencies | unvetted-dep:jora | AI (dependencies): jora is a long-standing dependency of statoscope tooling, pinned exact version. | ai | |
| phantom-deps | phantom-dep:@types/archy | AI (phantom-deps): Type declaration package, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type declaration package, not directly imported by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established helper lib in monorepo; sparse README is stylistic, not spam. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.28.1 | 5 / 0 | |
| 5.28.0 | 5 / 0 | |
| 5.25.0 | 5 / 0 | |
| 5.24.0 | 5 / 0 | |
| 5.23.0 | 5 / 0 | |
| 5.22.0 | 5 / 0 | |
| 5.14.1 | 5 / 0 | |
| 5.9.0 | 5 / 0 | |
| 5.7.1 | 5 / 0 | |
| 5.7.0 | 5 / 0 | |
| 5.6.1 | 2 / 0 | |
| 5.6.0 | 2 / 0 | |
| 5.5.1 | 1 / 1 | |
| 5.4.0 | 1 / 1 | |
| 5.3.0 | 0 / 0 | |
| 5.2.0 | 0 / 0 | |
| 5.1.0 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.23.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.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.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.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.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.4.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.