@nmtjs/application
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Used in a module-loader pattern loading implementation by filepath; stable across versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package with 88 versions; missing metadata is a style choice, not a spam indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA/Sigstore attestation; legitimate CI/CD automation for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a major version bump with SLSA provenance; consistent with intentional release cadence. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 6 / 1 | |
| 0.14.5 | 0 / 8 | |
| 0.14.4 | 0 / 7 | |
| 0.14.3 | 0 / 7 | |
| 0.14.2 | 0 / 7 | |
| 0.14.1 | 0 / 7 | |
| 0.14.0 | 0 / 7 | |
| 0.13.1 | 0 / 7 | |
| 0.13.0 | 0 / 7 | |
| 0.12.9 | 0 / 7 | |
| 0.12.8 | 0 / 7 | |
| 0.12.7 | 0 / 7 | |
| 0.12.6 | 0 / 7 | |
| 0.12.5 | 0 / 7 | |
| 0.12.4 | 0 / 7 | |
| 0.12.2 | 0 / 7 | |
| 0.12.1 | 0 / 7 | |
| 0.12.0 | 0 / 7 | |
| 0.11.9 | 0 / 7 | |
| 0.11.8 | 0 / 7 | |
| 0.11.7 | 0 / 7 | |
| 0.11.6 | 0 / 7 | |
| 0.11.5 | 0 / 7 | |
| 0.11.4 | 0 / 7 | |
| 0.11.3 | 0 / 7 | |
| 0.11.2 | 0 / 7 | |
| 0.11.1 | 0 / 7 | |
| 0.11.0 | 0 / 7 | |
| 0.10.5 | 0 / 7 | |
| 0.10.4 | 0 / 7 |
v0.16.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.