ses
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish; gitHead absence is environment-dependent, not a security signal for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with known maintainers; dormancy reflects release cadence, not compromise. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): 'ses' is a well-known acronym for Secure EcmaScript Shim, a legitimate security package from Agoric/Endo. Not a typosquat of 'jest'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 'ses' is a well-known acronym for Secure EcmaScript Shim, a legitimate security package from Agoric/Endo. Not a typosquat of 'qs'. | ai | |
| dependencies | unvetted-dep:@endo/env-options | AI (dependencies): @endo/env-options is a first-party dependency from the same Endo monorepo (endojs/endo) that publishes ses. Not a suspicious third-party dependency. | ai | |
| dependencies | unvetted-dep:@endo/immutable-arraybuffer | AI (dependencies): @endo/immutable-arraybuffer is a first-party dependency from the same Endo monorepo (endojs/endo) that publishes ses. Not a suspicious third-party dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 3 / 0 | |
| 2.0.0 | 3 / 15 | |
| 1.15.0 | 3 / 15 | |
| 1.14.0 | 3 / 22 | |
| 1.13.1 | 2 / 22 | |
| 1.13.0 | 2 / 22 | |
| 1.12.0 | 1 / 22 |
v2.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boneskull.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (boneskull) than the most recent previously approved version (mhofman) on 2026-05-27, but boneskull is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.