stentor-handler
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.72.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.