@monstermann/signals-modal
Composable modal management.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance is absent but common; not a disqualifier for this established package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate scoped package with repo and exports; README/keywords gaps are cosmetic, not spam. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Part of a scoped monorepo (@monstermann/*); 0.0.0 is the intentional initial version across the ecosystem, not a malware indicator. | ai | |
| dependencies | unvetted-dep:@monstermann/dfdl | AI (dependencies): Same-author scoped dependency; consistent with a personal package ecosystem, not a supply-chain injection. | ai | |
| dependencies | unvetted-dep:@monstermann/signals-web | AI (dependencies): Same-author scoped dependency; consistent with a personal package ecosystem. | ai | |
| dependencies | unvetted-dep:@monstermann/signals | AI (dependencies): Same-author scoped dependency; consistent with a personal package ecosystem. | ai | |
| dependencies | unvetted-dep:@monstermann/geometry | AI (dependencies): Same-author scoped dependency; consistent with a personal package ecosystem. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 4 / 2 | |
| 0.7.0 | 4 / 2 | |
| 0.6.0 | 4 / 2 | |
| 0.4.5 | 4 / 2 | |
| 0.4.2 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.3 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.0.0 | 3 / 2 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.