@abi-software/map-side-bar
[](https://badge.fury.io/js/%40abi-software%2Fmap-side-bar)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@abi-software/gallery | AI (dependencies): Same-org dependency from ABI-Software; consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:@abi-software/svg-sprite | AI (dependencies): Same-org dependency from ABI-Software; consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:@abi-software/map-utilities | AI (dependencies): Same-org dependency from ABI-Software; consistent across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 378 versions; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@abi-software/gallery | AI (phantom-deps): Same-org dependency; likely used transitively or via config rather than direct import. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Utility dep declared in package.json; referenced in config, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@abi-software/svg-sprite | AI (phantom-deps): Same-org dependency; likely used transitively or via config rather than direct import. | ai | |
| phantom-deps | phantom-dep:xss | AI (phantom-deps): Security sanitization lib declared in package.json; referenced in config, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Markdown rendering dep declared in package.json; referenced in config, stable false positive for this package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 12 / 21 | |
| 2.15.0 | 12 / 21 | |
| 2.14.7 | 12 / 21 | |
| 2.14.6 | 12 / 21 | |
| 2.14.5 | 12 / 21 | |
| 2.14.4 | 12 / 21 | |
| 2.14.3 | 12 / 21 | |
| 2.14.2 | 12 / 21 | |
| 2.14.1 | 12 / 21 | |
| 2.14.0 | 12 / 21 | |
| 2.13.0 | 12 / 21 | |
| 2.12.4 | 12 / 21 | |
| 2.12.2 | 12 / 21 | |
| 2.12.0 | 12 / 21 | |
| 2.11.4 | 12 / 21 | |
| 2.11.3 | 12 / 21 | |
| 2.11.2 | 12 / 21 | |
| 2.11.0 | 12 / 21 | |
| 2.10.5 | 12 / 21 | |
| 2.10.4 | 12 / 21 | |
| 2.10.3 | 12 / 21 | |
| 2.10.2 | 12 / 21 | |
| 2.10.1 | 12 / 21 | |
| 2.10.0 | 12 / 21 | |
| 2.9.1 | 12 / 21 | |
| 2.9.0 | 12 / 21 | |
| 2.8.2 | 12 / 21 | |
| 2.8.1 | 12 / 21 | |
| 2.8.0 | 12 / 21 | |
| 2.7.2 | 12 / 21 | |
| 2.7.1 | 12 / 21 | |
| 2.7.0 | 12 / 21 | |
| 2.6.3 | 11 / 21 | |
| 2.6.2 | 11 / 21 | |
| 2.6.1 | 11 / 21 | |
| 2.6.0 | 11 / 21 | |
| 2.5.2 | 11 / 21 | |
| 2.5.1 | 11 / 21 | |
| 2.5.0 | 11 / 21 | |
| 2.4.2 | 11 / 21 | |
| 2.4.1 | 11 / 23 | |
| 2.4.0 | 11 / 23 | |
| 2.3.1 | 10 / 23 | |
| 2.3.0 | 10 / 23 | |
| 2.2.0 | 10 / 19 | |
| 2.1.0 | 10 / 19 |
v2.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.