stentor-logger
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long publish history; lack of Sigstore provenance is consistent across all versions. | ai |
Versions (showing 100 of 190)
| Version | Deps | Published |
|---|---|---|
| 1.74.1 | 1 / 11 | |
| 1.74.0 | 1 / 11 | |
| 1.73.0 | 1 / 11 | |
| 1.72.4 | 1 / 11 | |
| 1.72.3 | 1 / 11 | |
| 1.72.1 | 2 / 11 | |
| 1.72.0 | 2 / 11 | |
| 1.71.0 | 2 / 11 | |
| 1.69.19 | 2 / 11 | |
| 1.69.14 | 2 / 11 | |
| 1.69.9 | 2 / 11 | |
| 1.69.7 | 2 / 11 | |
| 1.69.6 | 2 / 11 | |
| 1.69.5 | 2 / 11 | |
| 1.69.0 | 2 / 11 | |
| 1.68.29 | 2 / 11 | |
| 1.68.23 | 2 / 11 | |
| 1.68.6 | 2 / 11 | |
| 1.68.0 | 2 / 11 | |
| 1.67.0 | 2 / 11 | |
| 1.66.50 | 2 / 11 | |
| 1.66.49 | 2 / 11 | |
| 1.66.46 | 2 / 11 | |
| 1.66.41 | 2 / 11 | |
| 1.66.37 | 2 / 11 | |
| 1.66.35 | 2 / 11 | |
| 1.66.30 | 2 / 11 | |
| 1.66.25 | 2 / 11 | |
| 1.66.24 | 2 / 11 | |
| 1.66.22 | 2 / 11 | |
| 1.66.14 | 2 / 11 | |
| 1.66.12 | 2 / 11 | |
| 1.66.10 | 2 / 11 | |
| 1.66.7 | 2 / 11 | |
| 1.66.2 | 2 / 11 | |
| 1.66.0 | 2 / 11 | |
| 1.65.11 | 2 / 11 | |
| 1.65.9 | 2 / 11 | |
| 1.65.7 | 2 / 11 | |
| 1.65.0 | 2 / 11 | |
| 1.64.0 | 2 / 11 | |
| 1.61.16 | 2 / 11 | |
| 1.61.15 | 2 / 11 | |
| 1.61.13 | 3 / 11 | |
| 1.61.12 | 3 / 11 | |
| 1.61.11 | 3 / 11 | |
| 1.61.10 | 3 / 11 | |
| 1.61.9 | 3 / 11 | |
| 1.61.8 | 3 / 11 | |
| 1.61.7 | 3 / 11 | |
| 1.61.5 | 3 / 11 | |
| 1.61.3 | 3 / 11 | |
| 1.61.2 | 3 / 11 | |
| 1.61.1 | 3 / 11 | |
| 1.61.0 | 3 / 11 | |
| 1.60.59 | 3 / 11 | |
| 1.60.57 | 3 / 11 | |
| 1.60.56 | 3 / 11 | |
| 1.60.55 | 3 / 11 | |
| 1.60.54 | 3 / 11 | |
| 1.60.52 | 3 / 11 | |
| 1.60.51 | 3 / 11 | |
| 1.60.49 | 3 / 11 | |
| 1.60.48 | 3 / 11 | |
| 1.60.47 | 3 / 11 | |
| 1.60.46 | 3 / 11 | |
| 1.60.45 | 3 / 11 | |
| 1.60.44 | 3 / 11 | |
| 1.60.43 | 3 / 11 | |
| 1.60.42 | 3 / 11 | |
| 1.60.40 | 3 / 11 | |
| 1.60.39 | 3 / 11 | |
| 1.60.38 | 3 / 11 | |
| 1.60.37 | 3 / 11 | |
| 1.60.36 | 3 / 11 | |
| 1.60.35 | 3 / 11 | |
| 1.60.33 | 3 / 11 | |
| 1.60.32 | 3 / 11 | |
| 1.60.31 | 3 / 11 | |
| 1.60.30 | 3 / 11 | |
| 1.60.29 | 3 / 11 | |
| 1.60.28 | 3 / 11 | |
| 1.60.27 | 3 / 11 | |
| 1.60.26 | 3 / 11 | |
| 1.60.25 | 3 / 11 | |
| 1.60.24 | 3 / 11 | |
| 1.60.23 | 3 / 11 | |
| 1.60.22 | 3 / 11 | |
| 1.60.21 | 3 / 11 | |
| 1.60.20 | 3 / 11 | |
| 1.60.19 | 3 / 11 | |
| 1.60.16 | 3 / 11 | |
| 1.60.15 | 3 / 11 | |
| 1.60.14 | 3 / 11 | |
| 1.60.13 | 3 / 11 | |
| 1.60.12 | 3 / 11 | |
| 1.60.11 | 3 / 11 | |
| 1.60.9 | 3 / 11 | |
| 1.60.8 | 3 / 11 | |
| 1.60.7 | 3 / 11 |
v1.74.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.74.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (michaelmyers) on 2026-07-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.