@apipass/event-notification
> TODO: description
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): crypto-js is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.0.108 | 4 / 3 | |
| 0.0.107 | 4 / 3 | |
| 0.0.106 | 4 / 3 | |
| 0.0.104 | 4 / 3 | |
| 0.0.103 | 4 / 3 | |
| 0.0.102 | 4 / 3 | |
| 0.0.101 | 4 / 3 | |
| 0.0.100 | 4 / 3 | |
| 0.0.99 | 4 / 3 | |
| 0.0.98 | 4 / 3 | |
| 0.0.97 | 4 / 3 | |
| 0.0.96 | 4 / 3 | |
| 0.0.95 | 4 / 3 | |
| 0.0.94 | 4 / 3 | |
| 0.0.93 | 4 / 3 | |
| 0.0.92 | 4 / 3 | |
| 0.0.91 | 4 / 3 | |
| 0.0.90 | 4 / 3 | |
| 0.0.89 | 4 / 3 | |
| 0.0.88 | 4 / 3 | |
| 0.0.87 | 4 / 3 | |
| 0.0.86 | 4 / 3 | |
| 0.0.79 | 4 / 3 | |
| 0.0.78 | 3 / 3 | |
| 0.0.77 | 3 / 3 | |
| 0.0.76 | 3 / 3 | |
| 0.0.75 | 3 / 3 | |
| 0.0.74 | 3 / 3 | |
| 0.0.73 | 3 / 3 | |
| 0.0.72 | 3 / 3 | |
| 0.0.71 | 3 / 3 | |
| 0.0.70 | 3 / 3 | |
| 0.0.69 | 3 / 3 | |
| 0.0.68 | 3 / 3 | |
| 0.0.67 | 3 / 3 | |
| 0.0.66 | 3 / 3 | |
| 0.0.61 | 3 / 3 | |
| 0.0.60 | 3 / 3 | |
| 0.0.59 | 3 / 3 | |
| 0.0.58 | 3 / 3 | |
| 0.0.57 | 3 / 3 | |
| 0.0.56 | 1 / 2 | |
| 0.0.55 | 1 / 2 | |
| 0.0.54 | 1 / 2 | |
| 0.0.53 | 1 / 2 | |
| 0.0.52 | 1 / 2 | |
| 0.0.51 | 1 / 2 | |
| 0.0.50 | 1 / 2 | |
| 0.0.49 | 1 / 2 | |
| 0.0.48 | 1 / 2 | |
| 0.0.47 | 1 / 2 | |
| 0.0.46 | 1 / 2 | |
| 0.0.45 | 1 / 2 | |
| 0.0.44 | 1 / 2 | |
| 0.0.43 | 1 / 2 | |
| 0.0.42 | 1 / 2 | |
| 0.0.41 | 1 / 2 | |
| 0.0.40 | 1 / 2 | |
| 0.0.39 | 1 / 2 | |
| 0.0.38 | 1 / 2 | |
| 0.0.37 | 1 / 2 | |
| 0.0.36 | 1 / 2 | |
| 0.0.35 | 1 / 2 | |
| 0.0.34 | 1 / 2 |
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.