map-schema
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:kind-of | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:arr-union | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:get-value | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:set-value | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:lazy-cache | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:mixin-deep | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:omit-empty | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:union-value | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:collection-visit | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| phantom-deps | phantom-dep:sort-object-arrays | AI (phantom-deps): Phantom deps in utility/schema libraries are common; dependencies used indirectly through config or transitive patterns. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected and not a security signal for this established package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 17 / 3 | |
| 0.2.4 | 20 / 7 | |
| 0.2.3 | 19 / 7 | |
| 0.2.2 | 18 / 7 | |
| 0.2.1 | 18 / 7 | |
| 0.2.0 | 16 / 7 | |
| 0.1.4 | 12 / 7 | |
| 0.1.3 | 11 / 7 | |
| 0.1.1 | 10 / 9 | |
| 0.1.0 | 10 / 9 |
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.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.