bser
JavaScript implementation of the BSER Binary Serialization
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 | publisher-changed | AI (provenance): kassens is a long-standing npm publisher (3842 days, 1030 approved packages) consistent with a legitimate internal Facebook/Meta maintainer transition for this Watchman-related package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer kassens has strong track record (1030 approved, 0 rejected); transition aligns with Facebook/Meta's Watchman project ownership. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package has 3894-day history and 7 versions; inflated-semver signal is false positive. README promotional content is minor. | ai | |
| dependencies | unvetted-dep:node-int64 | AI (dependencies): node-int64 is appropriate for binary serialization; dependency is stable and necessary. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.0.3 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-06-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.