flatgeobuf
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/doc/assets/navigation.js | AI (source-diff): TypeDoc-generated navigation index; base64 blob is standard doc tooling output, not a payload. | ai | |
| source-diff | encoded-string-file:dist/doc/assets/search.js | AI (source-diff): TypeDoc-generated search index; base64 blob is standard doc tooling output, not a payload. | ai | |
| phantom-deps | phantom-dep:slice-source | AI (phantom-deps): Used via type declarations and config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@repeaterjs/repeater | AI (phantom-deps): Runtime dep used indirectly; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 3 / 20 | |
| 4.3.4 | 3 / 22 | |
| 4.3.3 | 3 / 22 | |
| 4.3.1 | 3 / 22 | |
| 4.3.0 | 3 / 22 | |
| 4.2.0 | 3 / 22 | |
| 4.1.1 | 3 / 22 | |
| 4.1.0 | 3 / 22 | |
| 4.0.2 | 3 / 21 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.