express-session
Simple session middleware for 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rand-token | AI (dependencies): rand-token is a legitimate random token generation library, a natural replacement for uid2 in session ID generation. Pinned to exact version 0.2.1 by a trusted maintainer. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): safe-buffer is a well-known, trusted package by Feross Aboukhadijeh; its addition is a legitimate dependency for safe Buffer handling. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ulisesgascon is a known Express.js TC member; addition is part of the documented project revitalization, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers is consistent with the Express.js TC transition; dougwilson stepped back from active maintenance publicly. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with the Express.js project's reduced activity period before TC revitalization; not indicative of account compromise. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from dougwilson to ulisesgascon reflects the documented Express.js TC maintainer transition in 2024; legitimate for this package going forward. | ai | |
| provenance | no-provenance | AI (provenance): express-session is a well-known Express.js project; lack of Sigstore provenance is common and not a risk indicator for this established package. | ai | |
| dependencies | unvetted-dep:uid-safe | AI (dependencies): uid-safe is a standard secure UID generator, a core dependency of express-session for session ID generation; stable and expected. | ai | |
| dependencies | unvetted-dep:depd | AI (dependencies): depd is a well-established Express ecosystem utility for deprecation warnings; its use here is expected and benign. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 1.19.0 | 8 / 8 | |
| 1.18.2 | 8 / 8 | |
| 1.18.1 | 8 / 8 | |
| 1.18.0 | 8 / 8 | |
| 1.17.3 | 8 / 8 | |
| 1.17.2 | 8 / 8 | |
| 1.17.1 | 8 / 8 | |
| 1.17.0 | 8 / 8 | |
| 1.16.2 | 8 / 8 | |
| 1.16.1 | 8 / 8 | |
| 1.16.0 | 8 / 8 | |
| 1.15.6 | 9 / 8 | |
| 1.15.5 | 9 / 6 | |
| 1.15.4 | 9 / 6 | |
| 1.15.3 | 9 / 6 | |
| 1.15.2 | 9 / 6 | |
| 1.15.1 | 9 / 6 | |
| 1.15.0 | 9 / 6 | |
| 1.14.2 | 9 / 6 | |
| 1.14.1 | 9 / 6 | |
| 1.14.0 | 9 / 6 | |
| 1.13.0 | 9 / 6 | |
| 1.12.1 | 9 / 6 | |
| 1.12.0 | 9 / 6 | |
| 1.11.3 | 9 / 6 | |
| 1.11.2 | 9 / 6 | |
| 1.11.1 | 9 / 6 | |
| 1.11.0 | 9 / 6 | |
| 1.10.4 | 9 / 6 | |
| 1.10.3 | 9 / 6 | |
| 1.10.2 | 9 / 6 | |
| 1.10.1 | 9 / 6 | |
| 1.10.0 | 9 / 6 | |
| 1.9.3 | 9 / 7 | |
| 1.9.2 | 9 / 7 | |
| 1.9.1 | 9 / 7 | |
| 1.9.0 | 9 / 7 | |
| 1.8.2 | 9 / 7 | |
| 1.8.1 | 9 / 7 | |
| 1.8.0 | 9 / 7 | |
| 1.7.6 | 9 / 7 | |
| 1.7.5 | 9 / 7 | |
| 1.7.4 | 8 / 7 | |
| 1.7.3 | 8 / 7 | |
| 1.7.2 | 8 / 7 | |
| 1.7.1 | 8 / 7 | |
| 1.7.0 | 8 / 7 | |
| 1.6.5 | 8 / 7 | |
| 1.6.4 | 8 / 7 | |
| 1.6.3 | 8 / 7 | |
| 1.6.2 | 8 / 7 | |
| 1.6.1 | 8 / 7 | |
| 1.6.0 | 8 / 7 | |
| 1.5.2 | 8 / 6 | |
| 1.5.1 | 8 / 6 | |
| 1.5.0 | 8 / 6 | |
| 1.4.0 | 7 / 6 | |
| 1.3.1 | 7 / 6 | |
| 1.3.0 | 7 / 6 | |
| 1.2.1 | 7 / 5 | |
| 1.2.0 | 7 / 5 | |
| 1.1.0 | 6 / 5 | |
| 1.0.4 | 6 / 5 | |
| 1.0.3 | 6 / 5 | |
| 1.0.2 | 6 / 5 | |
| 1.0.1 | 5 / 6 | |
| 1.0.0 | 1 / 6 |
v1.18.1
2 findingsThis version was published by a different npm account than previous versions on 2024-10-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.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.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
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.0.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.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.
v1.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.
v1.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.