@abi-software/flatmapvuer
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@esbuild/linux-x64 | AI (phantom-deps): Platform-specific optional binary; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@rollup/rollup-linux-x64-gnu | AI (phantom-deps): Platform-specific optional rollup binary; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:css-element-queries | AI (phantom-deps): css-element-queries is a declared runtime dep used via config/indirect import; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.13.4 | 10 / 18 | |
| 1.13.3 | 10 / 18 | |
| 1.13.2 | 10 / 18 | |
| 1.13.1 | 10 / 18 | |
| 1.13.0 | 10 / 18 | |
| 1.12.2 | 10 / 18 | |
| 1.12.1 | 10 / 18 | |
| 1.12.0 | 10 / 18 | |
| 1.11.4 | 12 / 18 | |
| 1.11.3 | 10 / 18 | |
| 1.11.2 | 10 / 18 | |
| 1.11.1 | 10 / 18 | |
| 1.11.0 | 10 / 18 | |
| 1.10.2 | 10 / 18 | |
| 1.10.1 | 10 / 18 | |
| 1.10.0 | 10 / 18 |
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.