stentor-utils
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:@types/xmldoc | AI (phantom-deps): @types/xmldoc is a type-only dep used at compile time; not imported at runtime by convention. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with clean history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 100 of 179)
| Version | Deps | Published |
|---|---|---|
| 1.74.0 | 19 / 21 | |
| 1.73.0 | 19 / 21 | |
| 1.72.4 | 19 / 21 | |
| 1.72.3 | 19 / 21 | |
| 1.72.0 | 19 / 21 | |
| 1.69.19 | 19 / 21 | |
| 1.69.14 | 19 / 21 | |
| 1.69.9 | 19 / 21 | |
| 1.69.7 | 19 / 21 | |
| 1.69.6 | 19 / 21 | |
| 1.69.5 | 19 / 21 | |
| 1.69.0 | 19 / 21 | |
| 1.68.29 | 19 / 21 | |
| 1.68.23 | 19 / 21 | |
| 1.68.6 | 19 / 21 | |
| 1.68.0 | 19 / 21 | |
| 1.66.46 | 21 / 21 | |
| 1.66.41 | 21 / 21 | |
| 1.66.37 | 21 / 21 | |
| 1.66.35 | 21 / 21 | |
| 1.66.30 | 21 / 21 | |
| 1.66.25 | 21 / 21 | |
| 1.66.24 | 21 / 21 | |
| 1.66.22 | 21 / 21 | |
| 1.66.14 | 21 / 21 | |
| 1.66.12 | 21 / 21 | |
| 1.66.10 | 21 / 21 | |
| 1.66.7 | 21 / 21 | |
| 1.66.2 | 21 / 21 | |
| 1.66.0 | 21 / 21 | |
| 1.65.11 | 21 / 21 | |
| 1.65.9 | 21 / 21 | |
| 1.65.7 | 21 / 21 | |
| 1.65.0 | 21 / 21 | |
| 1.64.0 | 21 / 22 | |
| 1.61.16 | 21 / 22 | |
| 1.61.13 | 21 / 22 | |
| 1.61.12 | 21 / 22 | |
| 1.61.11 | 21 / 22 | |
| 1.61.10 | 21 / 22 | |
| 1.61.9 | 21 / 22 | |
| 1.61.8 | 21 / 22 | |
| 1.61.7 | 21 / 22 | |
| 1.61.5 | 21 / 22 | |
| 1.61.3 | 21 / 22 | |
| 1.61.2 | 21 / 22 | |
| 1.61.1 | 21 / 22 | |
| 1.61.0 | 21 / 22 | |
| 1.60.59 | 22 / 22 | |
| 1.60.57 | 22 / 22 | |
| 1.60.56 | 22 / 22 | |
| 1.60.55 | 22 / 22 | |
| 1.60.54 | 22 / 22 | |
| 1.60.52 | 22 / 22 | |
| 1.60.51 | 22 / 22 | |
| 1.60.49 | 22 / 22 | |
| 1.60.48 | 22 / 22 | |
| 1.60.47 | 22 / 22 | |
| 1.60.46 | 22 / 22 | |
| 1.60.45 | 22 / 22 | |
| 1.60.44 | 22 / 22 | |
| 1.60.43 | 22 / 22 | |
| 1.60.42 | 22 / 22 | |
| 1.60.40 | 22 / 22 | |
| 1.60.39 | 22 / 22 | |
| 1.60.38 | 22 / 22 | |
| 1.60.37 | 22 / 22 | |
| 1.60.36 | 22 / 22 | |
| 1.60.35 | 22 / 22 | |
| 1.60.33 | 22 / 22 | |
| 1.60.32 | 22 / 22 | |
| 1.60.31 | 22 / 22 | |
| 1.60.30 | 22 / 22 | |
| 1.60.29 | 22 / 22 | |
| 1.60.28 | 22 / 22 | |
| 1.60.27 | 22 / 22 | |
| 1.60.26 | 22 / 22 | |
| 1.60.25 | 22 / 22 | |
| 1.60.24 | 22 / 22 | |
| 1.60.23 | 22 / 22 | |
| 1.60.22 | 22 / 22 | |
| 1.60.21 | 22 / 22 | |
| 1.60.20 | 22 / 22 | |
| 1.60.19 | 22 / 22 | |
| 1.60.16 | 22 / 22 | |
| 1.60.15 | 22 / 22 | |
| 1.60.14 | 22 / 22 | |
| 1.60.13 | 22 / 22 | |
| 1.60.12 | 22 / 22 | |
| 1.60.11 | 22 / 22 | |
| 1.60.9 | 22 / 22 | |
| 1.60.8 | 22 / 22 | |
| 1.60.7 | 22 / 22 | |
| 1.60.6 | 22 / 22 | |
| 1.60.5 | 22 / 22 | |
| 1.60.3 | 22 / 22 | |
| 1.60.2 | 22 / 22 | |
| 1.60.1 | 22 / 22 | |
| 1.59.144 | 21 / 22 | |
| 1.59.143 | 21 / 22 |
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.
v1.60.6
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.5
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.3
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.2
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.1
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.59.144
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.59.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.