@fastnear/borsh
Lean borsh serializer/deserializer for NEAR Protocol
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): Monorepo publish script change explains missing gitHead; no other risk signals present. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped borsh serializer for NEAR Protocol; Levenshtein match to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 4 | |
| 1.1.4 | 0 / 4 | |
| 1.1.3 | 0 / 4 | |
| 1.1.2 | 0 / 4 | |
| 1.1.1 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.2 | 0 / 4 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 | |
| 0.10.4 | 0 / 4 | |
| 0.10.3 | 0 / 4 | |
| 0.10.2 | 0 / 4 | |
| 0.10.1 | 0 / 4 | |
| 0.10.0 | 0 / 4 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.