@vixoniccom/birthdays
Muestre cumpleaños de los miembros de su equipo.
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): Internal org package; no provenance is consistent across all 165 versions of this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Build-tool pattern; dependencies re-exported by @vixoniccom/module-packager. | ai | |
| phantom-deps | phantom-dep:animejs | AI (phantom-deps): Build-tool pattern; dependencies re-exported by @vixoniccom/module-packager. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Build-tool pattern; dependencies re-exported by @vixoniccom/module-packager. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package; minimal metadata is expected for this use case. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.7.12 | 3 / 7 | |
| 0.7.11 | 3 / 7 | |
| 0.7.8 | 3 / 7 | |
| 0.7.7 | 3 / 7 | |
| 0.7.6 | 3 / 7 | |
| 0.7.5 | 3 / 7 | |
| 0.7.4 | 4 / 6 | |
| 0.7.3 | 4 / 7 |
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.