@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| 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 | |
| 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 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 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.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.79 | 11 / 19 | |
| 5.0.71 | 11 / 19 | |
| 5.0.67 | 11 / 19 | |
| 5.0.59 | 11 / 19 | |
| 5.0.41 | 12 / 18 | |
| 5.0.35 | 12 / 18 | |
| 5.0.32 | 12 / 18 | |
| 5.0.29 | 12 / 18 | |
| 5.0.25 | 12 / 18 | |
| 5.0.23 | 12 / 18 | |
| 5.0.22 | 11 / 18 | |
| 5.0.20 | 11 / 18 | |
| 5.0.16 | 11 / 18 | |
| 5.0.15 | 11 / 18 | |
| 5.0.14 | 11 / 18 | |
| 5.0.9 | 11 / 18 | |
| 5.0.4 | 11 / 18 | |
| 5.0.3 | 11 / 18 |
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.