stentor-handler
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stentor-locales | AI (phantom-deps): Config-only reference in a monorepo-style package; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:stentor-conditional | AI (phantom-deps): Config-only reference in a monorepo-style package; not a real phantom dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stentor is a known ecosystem; sparse metadata is consistent across all its packages, not a spam signal. | ai | |
| phantom-deps | phantom-dep:stentor-context | AI (phantom-deps): Sibling monorepo package; referenced in config files is expected for this ecosystem. | ai | |
| phantom-deps | phantom-dep:stentor-storage | AI (phantom-deps): Sibling monorepo package; referenced in config files is expected for this ecosystem. | ai |
Versions (showing 100 of 201)
| Version | Deps | Published |
|---|---|---|
| 1.74.0 | 11 / 12 | |
| 1.73.0 | 11 / 12 | |
| 1.72.4 | 11 / 12 | |
| 1.72.3 | 11 / 12 | |
| 1.72.1 | 10 / 12 | |
| 1.72.0 | 10 / 12 | |
| 1.71.0 | 10 / 12 | |
| 1.69.19 | 10 / 12 | |
| 1.69.14 | 10 / 12 | |
| 1.69.9 | 10 / 12 | |
| 1.69.7 | 10 / 12 | |
| 1.69.6 | 10 / 12 | |
| 1.69.5 | 10 / 12 | |
| 1.69.0 | 10 / 12 | |
| 1.68.30 | 10 / 12 | |
| 1.68.29 | 10 / 12 | |
| 1.68.23 | 10 / 12 | |
| 1.68.20 | 10 / 12 | |
| 1.68.14 | 10 / 12 | |
| 1.68.9 | 10 / 12 | |
| 1.68.6 | 10 / 12 | |
| 1.68.2 | 12 / 12 | |
| 1.68.0 | 12 / 12 | |
| 1.67.0 | 12 / 12 | |
| 1.66.50 | 12 / 12 | |
| 1.66.49 | 12 / 12 | |
| 1.66.46 | 12 / 12 | |
| 1.66.41 | 12 / 12 | |
| 1.66.37 | 12 / 12 | |
| 1.66.35 | 12 / 12 | |
| 1.66.33 | 12 / 12 | |
| 1.66.30 | 12 / 12 | |
| 1.66.25 | 12 / 12 | |
| 1.66.24 | 12 / 12 | |
| 1.66.22 | 12 / 12 | |
| 1.66.16 | 12 / 12 | |
| 1.66.14 | 12 / 12 | |
| 1.66.12 | 12 / 12 | |
| 1.66.10 | 12 / 12 | |
| 1.66.7 | 12 / 12 | |
| 1.66.2 | 12 / 12 | |
| 1.66.0 | 12 / 12 | |
| 1.65.11 | 12 / 12 | |
| 1.65.9 | 12 / 12 | |
| 1.65.7 | 12 / 12 | |
| 1.65.0 | 12 / 12 | |
| 1.64.0 | 12 / 12 | |
| 1.61.16 | 12 / 12 | |
| 1.61.15 | 12 / 12 | |
| 1.61.14 | 12 / 12 | |
| 1.61.13 | 12 / 12 | |
| 1.61.12 | 12 / 12 | |
| 1.61.11 | 12 / 12 | |
| 1.61.10 | 12 / 12 | |
| 1.61.9 | 12 / 12 | |
| 1.61.8 | 12 / 12 | |
| 1.61.7 | 12 / 12 | |
| 1.61.6 | 12 / 12 | |
| 1.61.5 | 12 / 12 | |
| 1.61.4 | 12 / 12 | |
| 1.61.3 | 12 / 12 | |
| 1.61.2 | 12 / 12 | |
| 1.61.1 | 12 / 12 | |
| 1.61.0 | 12 / 12 | |
| 1.60.59 | 12 / 12 | |
| 1.60.57 | 12 / 12 | |
| 1.60.56 | 12 / 12 | |
| 1.60.55 | 12 / 12 | |
| 1.60.54 | 12 / 12 | |
| 1.60.53 | 12 / 12 | |
| 1.60.52 | 12 / 12 | |
| 1.60.51 | 12 / 12 | |
| 1.60.49 | 12 / 12 | |
| 1.60.48 | 12 / 12 | |
| 1.60.47 | 12 / 12 | |
| 1.60.46 | 12 / 12 | |
| 1.60.45 | 12 / 12 | |
| 1.60.44 | 12 / 12 | |
| 1.60.43 | 12 / 12 | |
| 1.60.42 | 12 / 12 | |
| 1.60.40 | 12 / 12 | |
| 1.60.39 | 12 / 12 | |
| 1.60.38 | 12 / 12 | |
| 1.60.37 | 12 / 12 | |
| 1.60.36 | 12 / 12 | |
| 1.60.35 | 12 / 12 | |
| 1.60.33 | 12 / 12 | |
| 1.60.32 | 12 / 12 | |
| 1.60.31 | 12 / 12 | |
| 1.60.30 | 12 / 12 | |
| 1.60.29 | 12 / 12 | |
| 1.60.28 | 12 / 12 | |
| 1.60.27 | 12 / 12 | |
| 1.60.26 | 12 / 12 | |
| 1.60.25 | 12 / 12 | |
| 1.60.24 | 12 / 12 | |
| 1.60.23 | 12 / 12 | |
| 1.60.22 | 12 / 12 | |
| 1.60.21 | 12 / 12 | |
| 1.60.20 | 12 / 12 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.