@discordjs/builders
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Official discordjs monorepo publish; gitHead absence is a harmless env change. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper dependency; its use as an implicit dependency in compiled TypeScript packages is expected and stable for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.14.1 | 7 / 15 | |
| 1.14.0 | 7 / 15 | |
| 1.13.1 | 7 / 15 | |
| 1.13.0 | 7 / 15 | |
| 1.12.2 | 7 / 15 | |
| 1.12.1 | 7 / 15 | |
| 1.12.0 | 7 / 15 | |
| 1.11.3 | 7 / 15 | |
| 1.11.2 | 7 / 15 | |
| 1.11.1 | 7 / 15 | |
| 1.11.0 | 7 / 15 | |
| 1.10.1 | 7 / 15 | |
| 1.10.0 | 7 / 15 | |
| 1.9.0 | 7 / 15 | |
| 1.8.2 | 7 / 15 | |
| 1.8.1 | 7 / 15 | |
| 1.8.0 | 7 / 15 | |
| 1.7.0 | 7 / 15 | |
| 1.6.5 | 7 / 15 | |
| 1.6.4 | 7 / 15 | |
| 1.6.3 | 7 / 14 | |
| 1.6.2 | 7 / 14 | |
| 1.6.1 | 7 / 14 | |
| 1.6.0 | 7 / 14 | |
| 1.5.0 | 7 / 14 | |
| 1.4.0 | 6 / 13 | |
| 1.3.0 | 6 / 13 | |
| 1.2.0 | 5 / 19 | |
| 1.1.0 | 5 / 12 | |
| 1.0.0 | 5 / 11 |
v1.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crawl.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.