stentor-history
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 113)
| Version | Deps | Published |
|---|---|---|
| 1.74.0 | 0 / 9 | |
| 1.73.0 | 0 / 9 | |
| 1.72.4 | 0 / 9 | |
| 1.72.3 | 0 / 9 | |
| 1.72.0 | 0 / 9 | |
| 1.71.0 | 0 / 9 | |
| 1.69.14 | 0 / 9 | |
| 1.69.9 | 0 / 9 | |
| 1.69.7 | 0 / 9 | |
| 1.69.6 | 0 / 9 | |
| 1.69.0 | 0 / 9 | |
| 1.68.23 | 0 / 9 | |
| 1.68.6 | 0 / 9 | |
| 1.67.0 | 0 / 9 | |
| 1.66.50 | 0 / 9 | |
| 1.66.49 | 0 / 9 | |
| 1.66.46 | 0 / 9 | |
| 1.66.41 | 0 / 9 | |
| 1.66.35 | 0 / 9 | |
| 1.66.30 | 0 / 9 | |
| 1.66.25 | 0 / 9 | |
| 1.66.24 | 0 / 9 | |
| 1.66.22 | 0 / 9 | |
| 1.66.14 | 0 / 9 | |
| 1.66.12 | 0 / 9 | |
| 1.66.10 | 0 / 9 | |
| 1.66.0 | 0 / 9 | |
| 1.65.11 | 0 / 9 | |
| 1.65.9 | 0 / 9 | |
| 1.65.7 | 0 / 9 | |
| 1.64.0 | 0 / 9 | |
| 1.61.16 | 0 / 9 | |
| 1.61.13 | 0 / 9 | |
| 1.61.12 | 0 / 9 | |
| 1.61.11 | 0 / 9 | |
| 1.61.9 | 0 / 9 | |
| 1.61.7 | 0 / 9 | |
| 1.61.2 | 0 / 9 | |
| 1.61.1 | 0 / 9 | |
| 1.60.59 | 0 / 9 | |
| 1.60.55 | 0 / 9 | |
| 1.60.48 | 0 / 9 | |
| 1.60.45 | 0 / 9 | |
| 1.60.44 | 0 / 9 | |
| 1.60.43 | 0 / 9 | |
| 1.60.39 | 0 / 9 | |
| 1.60.38 | 0 / 9 | |
| 1.60.35 | 0 / 9 | |
| 1.60.33 | 0 / 9 | |
| 1.60.32 | 0 / 9 | |
| 1.60.31 | 0 / 9 | |
| 1.60.30 | 0 / 9 | |
| 1.60.29 | 0 / 9 | |
| 1.60.26 | 0 / 9 | |
| 1.60.25 | 0 / 9 | |
| 1.60.24 | 0 / 9 | |
| 1.60.23 | 0 / 9 | |
| 1.60.22 | 0 / 9 | |
| 1.60.20 | 0 / 9 | |
| 1.60.16 | 0 / 9 | |
| 1.60.15 | 0 / 9 | |
| 1.60.14 | 0 / 9 | |
| 1.60.13 | 0 / 9 | |
| 1.60.12 | 0 / 9 | |
| 1.60.8 | 0 / 9 | |
| 1.60.7 | 0 / 9 | |
| 1.60.5 | 0 / 9 | |
| 1.60.2 | 0 / 9 | |
| 1.60.1 | 0 / 9 | |
| 1.59.144 | 0 / 9 | |
| 1.59.143 | 0 / 9 | |
| 1.59.141 | 0 / 9 | |
| 1.59.139 | 0 / 9 | |
| 1.59.135 | 0 / 9 | |
| 1.59.128 | 0 / 9 | |
| 1.59.125 | 0 / 9 | |
| 1.59.123 | 0 / 9 | |
| 1.59.122 | 0 / 9 | |
| 1.59.117 | 0 / 9 | |
| 1.59.115 | 0 / 9 | |
| 1.59.114 | 0 / 9 | |
| 1.59.113 | 0 / 9 | |
| 1.59.108 | 0 / 9 | |
| 1.59.107 | 0 / 9 | |
| 1.59.103 | 0 / 9 | |
| 1.59.102 | 0 / 9 | |
| 1.59.101 | 0 / 9 | |
| 1.59.100 | 0 / 9 | |
| 1.59.99 | 0 / 9 | |
| 1.59.98 | 0 / 9 | |
| 1.59.96 | 0 / 9 | |
| 1.59.92 | 0 / 9 | |
| 1.59.91 | 0 / 9 | |
| 1.59.90 | 0 / 9 | |
| 1.59.89 | 0 / 9 | |
| 1.59.88 | 0 / 9 | |
| 1.59.87 | 0 / 9 | |
| 1.59.86 | 0 / 9 | |
| 1.59.85 | 0 / 9 | |
| 1.59.84 | 0 / 9 |
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.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.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.