@taptap/node-configs
Shared configuration files for TapTap Node.js projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Pure JSON config distribution package; no deps, no code, and empty index.js are expected for this package type. | ai | |
| phantom-deps | phantom-dep:markdownlint-cli2 | AI (phantom-deps): Config-only package; markdownlint-cli2 is a peer tool referenced in exported JSON config, not imported directly. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai | |
| phantom-deps | phantom-dep:@biomejs/biome | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:commitlint-config-gitmoji | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai | |
| phantom-deps | phantom-dep:commitlint-plugin-gitmoji | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai | |
| phantom-deps | phantom-dep:autocorrect-node | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai | |
| phantom-deps | phantom-dep:gitmojis | AI (phantom-deps): Config-only package; deps are referenced in exported config files, not JS imports. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.2.15 | 7 / 0 | |
| 0.2.13 | 7 / 0 | |
| 0.2.12 | 6 / 0 | |
| 0.2.11 | 6 / 0 | |
| 0.2.10 | 4 / 0 | |
| 0.2.9 | 4 / 0 | |
| 0.2.7 | 4 / 0 | |
| 0.2.6 | 4 / 0 | |
| 0.2.5 | 4 / 0 | |
| 0.2.4 | 4 / 0 | |
| 0.2.3 | 4 / 0 | |
| 0.2.2 | 4 / 0 | |
| 0.2.1 | 4 / 0 | |
| 0.2.0 | 4 / 0 | |
| 0.1.6 | 0 / 0 | |
| 0.1.5 | 0 / 0 | |
| 0.1.4 | 0 / 0 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.2.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
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: xdanger.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.