@pulumi/auth0
A Pulumi package for creating and managing auth0 cloud resources.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:webhook-url | AI (semgrep): Fires on JSDoc example code in eventStream.js; not executed, stable false positive for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): pulumi-bot uses automated CI/CD pipelines; rapid successive publishes are expected and normal for this package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.49.0 | 1 / 3 | |
| 3.48.0 | 1 / 3 | |
| 3.47.0 | 1 / 3 | |
| 3.46.0 | 1 / 3 | |
| 3.26.0 | 1 / 3 | |
| 3.25.0 | 1 / 3 | |
| 3.24.0 | 1 / 3 | |
| 3.23.2 | 1 / 3 | |
| 3.23.1 | 1 / 3 | |
| 3.23.0 | 1 / 3 | |
| 3.22.0 | 1 / 3 | |
| 3.21.0 | 1 / 3 | |
| 3.20.0 | 1 / 3 | |
| 3.19.1 | 1 / 3 | |
| 3.19.0 | 1 / 3 | |
| 3.18.0 | 1 / 3 | |
| 3.17.1 | 1 / 3 | |
| 3.17.0 | 1 / 3 | |
| 3.16.0 | 1 / 3 | |
| 3.15.0 | 1 / 3 | |
| 3.14.0 | 1 / 3 | |
| 3.13.1 | 1 / 3 | |
| 3.13.0 | 1 / 3 | |
| 3.12.0 | 1 / 3 | |
| 3.11.0 | 1 / 3 | |
| 3.10.2 | 1 / 3 | |
| 3.10.1 | 1 / 3 | |
| 3.10.0 | 1 / 3 | |
| 3.9.0 | 1 / 3 | |
| 3.8.3 | 1 / 3 | |
| 3.8.2 | 1 / 3 | |
| 3.8.1 | 1 / 3 | |
| 3.8.0 | 1 / 3 | |
| 3.7.1 | 1 / 3 | |
| 3.7.0 | 1 / 3 | |
| 3.6.0 | 1 / 3 | |
| 3.5.1 | 1 / 3 | |
| 3.5.0 | 1 / 3 | |
| 3.4.0 | 1 / 3 | |
| 3.3.3 | 1 / 3 | |
| 3.3.2 | 1 / 3 | |
| 3.3.1 | 1 / 3 | |
| 3.3.0 | 1 / 3 | |
| 3.1.2 | 1 / 3 | |
| 3.1.1 | 1 / 3 | |
| 3.1.0 | 1 / 3 | |
| 3.0.0 | 1 / 3 |
v3.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
3 findingsHardcoded webhook URL suggests data exfiltration (matched inside a comment — likely documentation, not executed code) Source: https://github.com/pulumi/pulumi-auth0/blob/c97cf68876f729f5cd93334bbb3868db9f132133/eventStream.js#L63 61 | * ], 62 | * webhookConfiguration: { > 63 | * webhookEndpoint: "https://eof28wtn4v4506o.m.pipedream.net", 64 | * webhookAuthorization: { 65 | * method: "bearer",
Hardcoded webhook URL suggests data exfiltration (matched inside a comment — likely documentation, not executed code) Source: https://github.com/pulumi/pulumi-auth0/blob/c97cf68876f729f5cd93334bbb3868db9f132133/eventStream.js#L81 79 | * ], 80 | * webhookConfiguration: { > 81 | * webhookEndpoint: "https://eof28wtn4v4506o.m.pipedream.net", 82 | * webhookAuthorization: { 83 | * method: "bearer",
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.