@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 27 of 127)
| Version | Deps | Published |
|---|---|---|
| 5.0.26 | 12 / 18 | |
| 5.0.25 | 12 / 18 | |
| 5.0.24 | 12 / 18 | |
| 5.0.23 | 12 / 18 | |
| 5.0.22 | 11 / 18 | |
| 5.0.21 | 11 / 18 | |
| 5.0.20 | 11 / 18 | |
| 5.0.19 | 11 / 18 | |
| 5.0.18 | 11 / 18 | |
| 5.0.17 | 11 / 18 | |
| 5.0.16 | 11 / 18 | |
| 5.0.15 | 11 / 18 | |
| 5.0.14 | 11 / 18 | |
| 5.0.13 | 11 / 18 | |
| 5.0.12 | 11 / 18 | |
| 5.0.11 | 11 / 18 | |
| 5.0.10 | 11 / 18 | |
| 5.0.9 | 11 / 18 | |
| 5.0.8 | 11 / 18 | |
| 5.0.7 | 11 / 18 | |
| 5.0.6 | 11 / 18 | |
| 5.0.5 | 11 / 18 | |
| 5.0.4 | 11 / 18 | |
| 5.0.3 | 11 / 18 | |
| 5.0.2 | 11 / 18 | |
| 5.0.1 | 11 / 18 | |
| 5.0.0 | 11 / 18 |
v5.0.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.
v5.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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.
v5.0.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.
v5.0.18
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.17
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.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.
v5.0.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.
v5.0.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.
v5.0.10
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.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.