@xylabs/express
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Shim re-export to documented successor, consistent with description/deprecation notice. | ai | |
| dependencies | unvetted-dep:@ariestools/express | AI (dependencies): Declared successor package for this deprecated shim, not an unrelated dependency. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Expected: package intentionally converted to a thin re-export shim. | ai | |
| phantom-deps | phantom-dep:@types/express-serve-static-core | AI (phantom-deps): @types/express-serve-static-core is a TypeScript type package used by convention in Express ecosystems; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/connect | AI (phantom-deps): @types/connect is a TypeScript type package used by convention in Express ecosystems; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all xylabs packages; not a risk signal for this publisher. | ai | |
| dependencies | unvetted-dep:express-mung | AI (dependencies): express-mung is a known Express middleware; stable dependency for this package across versions. | ai |
Versions (showing 100 of 127)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 15 | |
| 8.0.1 | 1 / 15 | |
| 8.0.0 | 1 / 15 | |
| 7.0.8 | 1 / 23 | |
| 7.0.7 | 1 / 23 | |
| 7.0.6 | 1 / 23 | |
| 7.0.5 | 1 / 23 | |
| 7.0.4 | 1 / 23 | |
| 7.0.3 | 1 / 23 | |
| 7.0.2 | 3 / 20 | |
| 7.0.1 | 3 / 20 | |
| 7.0.0 | 3 / 20 | |
| 6.1.4 | 3 / 20 | |
| 6.1.3 | 3 / 18 | |
| 6.1.1 | 3 / 18 | |
| 6.1.0 | 3 / 18 | |
| 6.0.10 | 3 / 18 | |
| 6.0.9 | 3 / 18 | |
| 6.0.8 | 3 / 18 | |
| 6.0.7 | 3 / 18 | |
| 6.0.6 | 3 / 18 | |
| 6.0.5 | 3 / 18 | |
| 6.0.4 | 3 / 18 | |
| 6.0.3 | 3 / 18 | |
| 6.0.2 | 3 / 21 | |
| 6.0.1 | 3 / 21 | |
| 6.0.0 | 3 / 21 | |
| 5.1.5 | 3 / 21 | |
| 5.1.4 | 3 / 21 | |
| 5.1.3 | 3 / 21 | |
| 5.1.2 | 3 / 21 | |
| 5.1.1 | 3 / 20 | |
| 5.1.0 | 3 / 22 | |
| 5.0.102 | 3 / 22 | |
| 5.0.101 | 3 / 22 | |
| 5.0.100 | 3 / 23 | |
| 5.0.99 | 3 / 45 | |
| 5.0.98 | 10 / 15 | |
| 5.0.97 | 10 / 15 | |
| 5.0.95 | 10 / 16 | |
| 5.0.91 | 10 / 20 | |
| 5.0.89 | 10 / 18 | |
| 5.0.88 | 10 / 18 | |
| 5.0.87 | 10 / 18 | |
| 5.0.86 | 10 / 18 | |
| 5.0.84 | 10 / 18 | |
| 5.0.83 | 10 / 18 | |
| 5.0.82 | 12 / 17 | |
| 5.0.81 | 12 / 17 | |
| 5.0.80 | 11 / 19 | |
| 5.0.79 | 11 / 19 | |
| 5.0.78 | 11 / 19 | |
| 5.0.76 | 11 / 19 | |
| 5.0.75 | 11 / 19 | |
| 5.0.74 | 11 / 19 | |
| 5.0.73 | 11 / 19 | |
| 5.0.72 | 11 / 19 | |
| 5.0.71 | 11 / 19 | |
| 5.0.70 | 11 / 19 | |
| 5.0.69 | 11 / 19 | |
| 5.0.67 | 11 / 19 | |
| 5.0.66 | 11 / 19 | |
| 5.0.65 | 11 / 19 | |
| 5.0.64 | 11 / 19 | |
| 5.0.63 | 11 / 19 | |
| 5.0.62 | 11 / 19 | |
| 5.0.61 | 12 / 18 | |
| 5.0.60 | 11 / 19 | |
| 5.0.59 | 11 / 19 | |
| 5.0.58 | 11 / 19 | |
| 5.0.57 | 11 / 19 | |
| 5.0.56 | 11 / 19 | |
| 5.0.55 | 11 / 19 | |
| 5.0.54 | 12 / 18 | |
| 5.0.52 | 12 / 18 | |
| 5.0.51 | 12 / 18 | |
| 5.0.50 | 12 / 18 | |
| 5.0.49 | 12 / 18 | |
| 5.0.48 | 12 / 18 | |
| 5.0.47 | 12 / 18 | |
| 5.0.46 | 12 / 18 | |
| 5.0.45 | 12 / 18 | |
| 5.0.44 | 12 / 18 | |
| 5.0.43 | 12 / 18 | |
| 5.0.42 | 12 / 18 | |
| 5.0.41 | 12 / 18 | |
| 5.0.40 | 12 / 18 | |
| 5.0.39 | 12 / 18 | |
| 5.0.38 | 12 / 18 | |
| 5.0.37 | 12 / 18 | |
| 5.0.36 | 12 / 18 | |
| 5.0.35 | 12 / 18 | |
| 5.0.34 | 12 / 18 | |
| 5.0.33 | 12 / 18 | |
| 5.0.32 | 12 / 18 | |
| 5.0.31 | 12 / 18 | |
| 5.0.30 | 12 / 18 | |
| 5.0.29 | 12 / 18 | |
| 5.0.28 | 12 / 18 | |
| 5.0.27 | 12 / 18 |
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-04, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.102
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-04, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.