@vlalg-nimbus/nb-calendar
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:vem lavar a louca gamers | AI (email-domain): Analyzer misidentified the author display name as an email domain; no actual email domain is unclaimed here. | ai | |
| phantom-deps | phantom-dep:@vlalg-nimbus/bee-css-reset | AI (phantom-deps): Same-org sibling dependency; likely used indirectly via CSS/style imports in Vue SFCs. | ai | |
| phantom-deps | phantom-dep:@vlalg-nimbus/chameleon-grid-layout | AI (phantom-deps): Same-org sibling dependency; likely used indirectly via Vue component composition. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 3 / 15 | |
| 3.0.1 | 3 / 15 | |
| 3.0.0 | 3 / 15 | |
| 2.1.1 | 3 / 15 | |
| 2.1.0 | 3 / 15 | |
| 2.0.0 | 3 / 15 | |
| 1.1.0 | 3 / 15 | |
| 1.0.2 | 3 / 15 | |
| 1.0.1 | 3 / 15 | |
| 1.0.0 | 3 / 15 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsMaintainer email 'Vem Lavar a Louca Gamers' uses domain 'vem lavar a louca gamers' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.